DEVICES:
========
EHXDL - DLVJ1
EHXDZ - DZV11
EHXQN - DEQNA
EHXRQ - RQDX1 (RX50, RD51, RD52)
EVSAA - ATTACHer???

sim> att rq1 bl-t857d-de.img
sim> c
mou/over=id dua1:
 
%MOUNT-I-MOUNTED, UVAXDIAG_2   mounted on _DUA1:
 
$ dir dua1:<sys0.sysmaint>

Directory DUA1:<SYS0.SYSMAINT>

DIAGBOOT.EXE;1      EHSAA.EXE;1         EHXDL.EXE;1         EHXDL.HLP;1
EHXDZ.EXE;1         EHXDZ.HLP;1         EHXQN.EXE;1         EHXQN.HLP;1
EHXRQ.EXE;1         EHXRQ.HLP;1         EVSAA.HLP;1         

Total of 11 files.
 
$ type DUA1:<SYS0.SYSMAINT>*.hlp

DUA1:<SYS0.SYSMAINT>EHXDL.HLP;1
===============================
1 HELP
  EHXDL
                            
        This program checks the functionality of the DLVJ1  providing
        error messages that may aid in the repair of the device.  The
        diagnostic uses  the internal  loopback mode to check most of
        the circuitry of the device.

1 DEVICE

        This program will be runnable only on a MicroVAX I computer and with
        a VAX Diagnostic Supervisor of version  6.12 or later.  This program
        is a level 3  functional  diagnostic and will not support any device
        other than the DLVJ1.
   
2 DLVJ1

  Description:   DLVJ1 Asynchronous four-line communications interface
  link:      HUB
  Generic name:  TTa
  Additional information:
     QBUS CSR [octal 760000-777776]<776500>
     QBUS vector [octal 2-776]
     Number of data bits configured [7 or 8]<8>
     Number of stop bits configured [1 or 2]<1>
     Parity detection enabled <no>
     Even parity enabled <no>
  Tested by: EHXDL

1 REQUIREMENTS

  HARDWARE:            MicroVAX I processor with 512Kb of memory
                       DLVJ1 dual size board


  OPTIONAL HARDWARE:   H3270-A  turn around connector
                       Another terminal

  SOFTWARE:            Vax Diagnostic Supervisor V6.12 or later


1 EVENT

  There are no user-settable event flags.

1 QUICK

  This diagnostic does not use the VDS QUICK-pass flag.

1 SUMMARY

  This diagnostic does not produce a summary report.

1 MANUAL

  Test section ECHO (test 9) requires manual intervention.  An additional
  terminal must be connected to one of the channels  and the operator must
  enter characters finishing with a control-z to complete the test.

1 SECTIONS


  There are five sections to this diagnostic.   Sections "LOOPBACK" and
  "ALL" require an H3270-A loopback connector.  Section "ECHO" requires
  another terminal and manual intervention.

2 DEFAULT

  Used for minimal testing.  This section includes tests 1, 2, and 4.
  Logic not requiring any loopback is tested.

2 REGISTER

  Used for minimal testing.  This section includes tests 1, 2, and 4.
  Logic not requiring any loopback is tested.  This is exactly the same
  as the DEFAULT section.

2 LOOPBACK

  Used to test internal loopback.  Requires an H3270-A loopback connector.
  This section includes tests 3, 5, 6, 7 and 8.

2 ALL

  Used to test all internal circuitry.  Requires an H3270-A loopback
  connector.  This section includes tests 1, 2, 3, 4, 5, 6, 7 and 8.

2 ECHO

  Used to verify communications with an external terminal.  Requires
  manual intervention and another terminal.  The operator is requied
  to respond to one question  on the console and to enter characters
  on the external terminal.   The test completes when a control-z is 
  entered.  This section includes test 9 only.

1 ATTACHING 


  The following is an example of how to attach the device to be tested,
  and to load and run EHXDL (answers to hardware questions are typed in
  octal).

  DS> LOAD EHXDL                  ; load the diagnostic
  DS> ATTACH DLVJ1                ; attach the DLVJ1
  Device link? HUB                ; the option is linked to HUB
  Device name? TTA                ; the option is named unit A (range=A-Z)
  CSR? 776500                     ; the csr address is 776500
  Vector? 300                     ; vector address is 300 (range=000-770)  
  Number of data bits? 8          ; 8 bits per character
  Number of stop bits? 1          ; 1 stop bits
  Parity detection enabled? YES   ; parity enabled
  Even parity enabled? NO         ; even parity not selected (odd parity)
  DS> SEL TTA                     ; select device
  DS> START                       ; start the diagnostic

DUA1:<SYS0.SYSMAINT>EHXDZ.HLP;1
===============================
1 HELP
  EHXDZ
                            
        This program checks the functionality of the  DZV11 providing
        error messages that may aid in the repair of the device.  The
        diagnostic uses the internal loopback  mode to  check most of 
        the circuitry of the device.

1 DEVICE

        This program will be runnable only on a MicroVAX I computer and with
        a VAX Diagnostic Supervisor of version  6.12 or later.  This program
        is  a level 3 functional diagnostic and will  not support any device
        other than the DZV11.
   
2 DZV11

  Description:   DZV11 Asynchronous four-line communications interface
  link:      HUB
  Generic name:  TTa
  Additional information:
     QBUS CSR [octal 760000-777776]<760100>
     QBUS vector [octal 2-776]
  Tested by: EHXDZ

1 REQUIREMENTS

  HARDWARE:            MicroVAX I processor with 512Kb of memory
                       DZV11 M7957


  OPTIONAL HARDWARE:   H329 turn around connector
                       Another terminal

  SOFTWARE:            Vax Diagnostic Supervisor V6.12 or later


1 EVENT

  There are no user-settable event flags.

1 QUICK

  This diagnostic does not use the VDS QUICK-pass flag.

1 SUMMARY

  This diagnostic does not produce a summary report.

1 MANUAL

  Test section ECHO (test 22) requires manual intervention.  A terminal
  must be connected to one of the channels  and the operator must
  enter characters finishing with a control-z to complete the test.

1 SECTIONS

  This program consists of 22 tests in six sections.   The  default  and
  "INTERNAL" sections include test 1 thru 19.   Section  "ALL"  includes
  test 1 thru 21 and requires an H329 turn  around  connector.   Section 
  "MODEM" is test 20 and requires a h329 turn around  connector. Section 
  "STAGGERED" includes tests 20 and 21 and requires  an H329 turn around
  connector.  Section "ECHO" is test 22 and requires manual intervention
  and a terminal connected to a DZV11 channel.

2 DEFAULT

  Used for minimal testing.  This section includes tests 1 thru 19.
  Internal logic is tested.

2 INTERNAL

  Used for minimal testing.  This section includes tests 1 thru 19.
  Internal logic is tested.  This is exactly the same as the DEFAULT
  section.

2 MODEM

  Used to test the modem control feature.  Requires an H329 turn aournd
  connector.  This section includes test 20 only.

2 STAGGERED

  Used to test staggered loopback mode.  Requires an H329 turn around
  connector.  This section includes tests 20 and 21.

2 ALL

  Used to test all internal circuitry.  Requires an H329 turn around
  connector.  This section includes tests 1 thru 21.

2 ECHO

  Used to verify communications with an external terminal.  Requires
  manual intervention and a terminal.  The operator  is  required to
  respond  to one  question on  the console and to enter  characters
  on the  external  terminal.   The  test completes when a control-z 
  is entered.  This section includes test 22 only.

1 ATTACHING 


  The following is an example of how to attach the device to be tested,
  and to load and run EHXDZ (answers to hardware questions are typed in
  octal).

  DS> LOAD EHXDZ                  ; load the diagnostic
  DS> ATTACH DZV11                ; attach the DZV11
  Device link? HUB                ; the option is linked to HUB
  Device name? TTA                ; the option is named unit A (range=A-Z)
  CSR? 760100                     ; the csr address is 760100
  Vector? 300                     ; vector address is 300 (range=000-770)  
  DS> SEL TTA                     ; select device
  DS> START                       ; start the diagnostic

DUA1:<SYS0.SYSMAINT>EHXQN.HLP;1
===============================
1 HELP
  EHXQN

        This program checks the  functionality of the  DEQNA Ethernet-QBUS
        communications interface.  It does so by utilizing the DEQNA built
        in loopback  testing  modes: Setup  mode, Internal  loopback mode,
        Internal-Extended  loopback mode, and External  loopback mode.  In
        addition, a simple network confidence test is provided to loopback
        data over a working Ethernet to a  remote system.  This is a level
        3 diagnostic.

1 DEVICE

        This program will run  only on  a MicroVAX I  computer and  with a
        Vax Diagnostic Supervisor  of version 6.12 or later.  This program
        is a level 3 diagnostic.

        This program will support the following device ONLY:

2 DEQNA

 Description:   DEQNA Ethernet-to-QBUS communications interface

 link:      HUB
 Generic name:  XQa

 Additional information:
    QBUS CSR [octal 760000-777776]<774440>

 Tested by: EHXQN

1 REQUIREMENTS

  HARDWARE:    MicroVAX I processor with 512Kb of memory
               Module loopback connector (part number 70-21489-01)

  SOFTWARE:    Vax Diagnostic Supervisor V6.12 or later

1 EVENT

  Setting event flag one causes the diagnostic to suppress the printout
  of the module's Ethernet physical station address during test 3.  The
  default setting for this event flag is "cleared."

1 QUICK

  This diagnostic does not use the VDS QUICK-pass flag.

1 SUMMARY

  This diagnostic does not produce a summary report.

1 MANUAL

  The default test section may be run on a  DEQNA module without any
  external  cabling  required.  The  internal loopback test  section
  (INTERNAL) may also be run with no special setup required.

  The external  loopback test section(EXTERNAL) requires that a DEQNA
  module loopback connector (part number 70-21489-01) be installed on
  the module before testing is started.

  The network confidence test section(NETWORK) and loopback assistant
  utility test section(LOOPBACK) require  that the unit under test be
  completely connected to a functioning Ethernet. This setup includes
  a  bulkhead  assembly, transceiver  cable, and  an installed trans-
  ceiver on an Ethernet cable.

1 SECTIONS

  There are five sections provided in  this diagnostic, the  INTERNAL
  loopback section, the EXTERNAL loopback section, the  NETWORK con-
  fidence  section, the LOOPBACK  assistant  section, and the DEFAULT
  section.

  Note  that the DEFAULT section is exactly the same as  the INTERNAL
  section in this diagnostic.

2 DEFAULT

  The  DEFAULT test section is the same as  the INTERNAL test section
  in this diagnostic.  Enter  "HELP EHXQN SECTIONS INTERNAL" for more
  information.

2 INTERNAL

  This test section consists of those tests that can be run on a  UUT
  without any special  setup.  Testing includes device register test-
  ing, boot/diagnostic ROM access testing,  interrupt sanity testing,
  Setup mode  testing, internal  loopback mode testing,  internal-ext
  ended loopback mode testing, and Ethernet address  filtering  test-
  ing.

2 EXTERNAL

  This test section consists of external mode loopback testing.  This
  test section requires that a DEQNA module  loopback connector (part
  number 70-21489-01)  be installed  on the module before  testing is
  started.

2 NETWORK

  This test section is used to perform loopback data  operations to a
  remote  system  on the  Ethernet.   Ethernet  Configuration Testing
  Protocol packets are used  to perform the  test.  This test  may be
  run on an Ethernet that is being used for normal data transfers  at
  the same  time;  it's  operation is  transparent to other  Ethernet
  stations.

  This test is intended to be a simple confidence test that  data may
  be successfully transferred  from the system  under test to another
  system.

  This test section requires that  the unit under test be  completely
  connected to a functioning Ethernet. This setup includes a bulkhead
  assembly, transceiver  cable, and  an  installed  transceiver on an
  Ethernet cable.

  Additionally, this test requires the presence  on the network  of a
  remote system that will respond  to loopback  requests directed  to
  the "loopback  assistant"  multicast  address  (CF-00-00-00-00-00).
  This requirement may be met by running the LOOPBACK test section of
  this diagnostic on another  system on the  network before  starting
  the network confidence test section on the system under test.

2 LOOPBACK

  This test section is not a test section,  per se.  It is a  utility
  that allows the current node to function  as a loopback  assistant,
  responding to the "loopback assistant"  multicast  address.  It  is
  for use with the network confidence test section  (NETWORK) in  the
  situation where no loopback assistant is found on the network.

  To use this test section in conjunction with the network confidence
  test section, you must first start the  loopback test  section run-
  ning on one system in the network and then start  the network  test
  section running on the system you wish to test.  After the  network
  confidence test  section completes,  you will then  be required  to
  manually stop the loopback test section running on the remote node.

  This test section requires that  the unit under test be  completely
  connected to a functioning Ethernet. This setup includes a bulkhead
  assembly, transceiver  cable, and  an  installed  transceiver on an
  Ethernet cable.

1 ATTACH

  The following is an example of how to run this diagnostic:

  DS> LOAD EHXQN                  ; load the diagnostic
  DS> ATTACH DEQNA                ; attach the DEQNA
  Device link? HUB                ; the option is linked to HUB
  Device name? XQA                ; the option is named 'XQA'
  CSR? 774440                     ; the CSR address is 774440(8)
  DS> SELECT XQA                  ; select the device to test
  DS> START                       ; start the internal tests

DUA1:<SYS0.SYSMAINT>EHXRQ.HLP;1
===============================
1 HELP
  EHXRQ

        This program checks the functionality of the RQDX1 disk controller
        and  associated drives  (RX50, RD51, and RD52)  by  exercising the
        drives  in a manner similar  to a typical  user load.  The default
        test section is a multi-drive disk  exerciser.   Additionally, the
        capability of  formatting  RD51  and  RD52 disk drives is provided
        via a disk formatting test section.  This is a level 3 diagnostic.

        THE DEFAULT TEST OPERATION DESTROYS USER DATA ON A DISK IF THE DISK
        IS WRITE-ENABLED WHEN THE DIAGNOSTIC IS STARTED.  WRITE PROTECT ANY
        DISKS WITH MEANINGFULL DATA ON THEM BEFORE STARTING THE  DIAGNOSTIC
        AND THE TESTING ON THAT DRIVE WILL BE LIMITED TO READ-ONLY TESTING.

1 DEVICE

        This program will run  only on  a MicroVAX I  computer and  with a
        Vax Diagnostic Supervisor  of version 6.12 or later.  This program
        is a level 3 diagnostic.

        This program will support the  following devices ONLY:

2 RD51

 Description:   RD51 fixed media disk (RQDX1)
 link:      DUa
 Generic name:  DUan
 Tested by: EHXRQ

2 RD52

 Description:   RD52 fixed media disk (RQDX1)
 link:      DUa
 Generic name:  DUan
 Tested by: EHXRQ

2 RQDX1

 Description:   RQDX1 QBUS MSCP disk controller
 link:      HUB
 Generic name:  DUa
 Additional information:
    QBUS IP register address [octal 760000-777776]<772150>
 Tested by: EHXRQ

2 RX50

 Description:   RX50 removable media disk (RQDX1)
 link:      DUa
 Generic name:  DUan
 Tested by: EHXRQ

1 REQUIREMENTS

  HARDWARE:    MicroVAX I processor with 512Kb of memory
               RQDX1 Disk Controller (M8639)
               One or more RD51, RD52, or RX50 drives

  SOFTWARE:    Vax Diagnostic Supervisor V6.12 or later

1 EVENT

  There are no user-settable event flags.

1 QUICK

  This diagnostic does not use the VDS QUICK-pass flag.

1 SUMMARY

  A summary report is generated when running the exerciser portion of
  the diagnostic.  It is output at the end of  testing or  whenever a
  user issues a VDS SUMMARY command.  No summary  report  is produced
  when the FORMATTER section is run.

  The summary report consists of a table with one line  for each disk
  drive under test.  The output looks like:

          Bytes      Bytes        Total  Soft     Hard
  Drive   Read       Written      Bytes  Errors   Errors
  -----   -----      -------      -----  ------   ------

  _DUA0   123456      245677     369133    0        0
  _DUA2   250456           0     250456    0       10     DROPPED


  The meaning of each column may be acquired by issuing a "HELP EHXRQ
  SUMMARY <topic>" command.

2 DRIVE

  This is the drive name testing was performed on.

2 BYTES_READ

  The total number of bytes of READ  or ACCESS commands  performed on
  the drive during testing.

2 BYTES_WRITTEN

  The total number of bytes of WRITE commands performed on  the drive
  during testing.  Drives  that are WRITE-PROTECTED  when the program
  is started are READ-ONLY  tested and this  column will  be zero for
  any such drives.

2 TOTAL_BYTES

  The total of the "Bytes Read" and "Bytes Written" columns.

2 SOFT_ERRORS

  The total number of WRITE errors detected by the software after re-
  reading the data written and discovering a data mismatch.

2 HARD_ERRORS

  The total number of hardware-detected errors on the drive.  Typical
  errors include drive-not-ready and/or  RQDX1-detected data  compare
  failures.  These errors are the result of the controller  returning
  a non-zero packet status in a command response or are the result of
  an operation timing out.

2 COMMENTS

  This last unlabeled column may contain the word "DROPPED" to denote
  a drive that has been dropped from testing as the  result of an ex-
  cessive number of errors detected during testing.

1 MANUAL

  All test sections should be considered manual intervention sections
  in that the user must ensure that  the appropriate media  is loaded
  into each SELECTED drive before starting the program.

  THE DEFAULT TEST OPERATION DESTROYS USER DATA ON A DISK IF THE DISK
  IS WRITE-ENABLED WHEN THE DIAGNOSTIC IS STARTED.  WRITE PROTECT ANY
  DISKS WITH MEANINGFULL DATA ON THEM BEFORE STARTING THE  DIAGNOSTIC
  AND THE TESTING ON THAT DRIVE WILL BE LIMITED TO READ-ONLY TESTING.
  

1 SECTIONS

  There are three sections provided in this diagnostic, the EXERCISER
  section, the FORMATTER section, and the DEFAULT section.

  Note  that the DEFAULT section is exactly the same as the EXERCISER
  section in this diagnostic.

2 DEFAULT

  The  DEFAULT test section is the same as the EXERCISER test section
  in this diagnostic.  Enter "HELP EHXRQ SECTIONS EXERCISER" for more
  information.

2 EXERCISER

  This  section is used  to simulate a typical I/O load on the user's
  disk drives.  All selected disk drives are subjected to a series of
  random READ, WRITE (if disk is write-enabled), and ACCESS commands.

  NOTE THAT DISKS THAT ARE WRITE-ENABLED MUST BE SCRATCH, AS ALL DATA
  ON  THEM  WILL BE DESTROYED AS THE RESULT OF THE TESTING OPERATION.
  WRITE  PROTECT ANY SENSITIVE  DISKS (INCLUDING THE DIAGNOSTIC DIST-
  RIBUTION  DISKS) ON DRIVES  THAT ARE  SELECTED BEFORE STARTING THIS
  TEST SECTION.

  Note that the EXERCISER section is also the DEFAULT section in this
  diagnostic.

  After  starting this  section, the  user  is asked to confirm write
  testing on  a disk drive for  each disk drive that is write enabled
  when  the  diagnostic is started.  Answering in the negative causes
  the test to be aborted.

2 FORMATTER

  This  test section is used to hardware-format RD51 and RD52 drives.
  Formatting  RX50 floppy  diskettes is NOT SUPPORTED.  Attempting to
  format an RX50 will result in a fatal error message being output by
  the diagnostic.

  FORMATTING A DISK DESTROYS ANY EXISTING DATA ON THE DISK.  You will
  be  asked to confirm  destroying  any existing data on the disk for
  each drive selected.

  Formatting an RD51 disk takes approximately 11 minutes.  Formatting
  an RD52 disk takes approximately 25 minutes.

1 ATTACH

  The  following  is an example  of how to ATTACH the RQDX1 and disks
  to be tested or  formatted.  The RQDX1 controller is first ATTACHED
  to the HUB and the drives to be tested or formatted are ATTACHED to
  the RQDX1.  The drives to be tested are then SELECTED and the diag-
  nostic is started.

  DS> LOAD EHXRQ                  ; load the diagnostic
  DS> ATTACH RQDX1                ; attach the RQDX1
  Device link? HUB                ; the option is linked to HUB
  Device name? DUA                ; the option is named 'DUA'
  IP? 772150                      ; the IP CSR address is 772150(8)
  DS> ATTACH RD51                 ; attach the RD51
  Device link? DUA                ; the option is linked to above RQDX1
  Device name? DUA0               ; the option is named 'DUA0'
  DS> ATTACH RX50                 ; attach the second RX50 drive
  Device link? DUA                ; the option is linked to above RQDX1
  Device name? DUA2               ; the option is named 'DUA2'
  DS> SELECT DUA0,DUA2            ; select the drives to be tested
  DS> START                       ; start the EXERCISER running

DUA1:<SYS0.SYSMAINT>EVSAA.HLP;1
===============================
1 ABORT
 Calls the program's cleanup code, then enters Supervisor  command  wait
 state.  The program can not be CONTINUEd.

 Format:
    ABORT
1 ATTACH
 Specifies the hardware characteristics of, and the  path  to,  a
 UUT  (Unit  Under Test) to be used by the Supervisor and/or by a
 program.

 Each device has a "link", which it  attaches  to.   Unless  this
 link  is the HUB (or SBI, CMI, or other legal synonyms thereof),
 the link device  must  have  been  previously  attached  itself.
 Therefore,  the  ATTACH  database  grows  in  a  branching  tree
 structure, outwards from the main system bus.

 Type "HELP DEVICE"  for  detailed  information  on  ATTACHing  a
 particular  device  known  to  the  Supervisor, or "HELP program
 DEVICE" for information on ATTACHing  a  device  specific  to  a
 program.

 Format:
    ATTACH UUT-type link-name generic-name [device-specific]
2 Parameters
 UUT-type
   The standard hardware designator for  the  device  to  be
   attached.

   Examples:
    RH780, DW780, TE16, RK07

 link-name
   The generic  device  name  connecting  the  UUT,  usually
   through intermediate links, to the main bus.

   Examples:
    DW0, RH0, MTA, HUB, DMA

 generic-name
   Uniquely identifies the particular device being ATTACHed,
   by   device   mnemonic,   and   controller  and  unit  if
   appropriate.

   Examples:
    DW0, RH0, DMA0, TTB1, MTA

   Type "HELP SPECIFY DEVICE"  for  information  on  generic
   name conventions.

 device-specific
   Some devices require specialized information to allow the
   Supervisor  or  program  to  access the device correctly.
   For example,  a  device  attached  directly  to  the  HUB
   requires  HUB TR (slot) and BR numbers; a device attached
   directly to the UNIBUS requires UNIBUS CSR,  vector,  and
   BR  numbers.  If information required for a device is not
   included in  the  ATTACH  command,  the  Supervisor  will
   prompt  individually  for  the required data.  Type "HELP
   DEVICE" or  "HELP  program  DEVICE"  for  information  on
   devices.
1 CLEAR
 Alters characteristics of Supervisor and/or program by  clearing
 flags, breakpoints, etc.

 Format:
    CLEAR option
2 BREAKPOINT
 Clears the program breakpoint set at the specified address

 Format:
    CLEAR BREAKPOINT address
3 Parameters
 address
   The address at which  the  breakpoint  was  set,  or  the
   keyword "ALL" to remove all breakpoints.
2 ENFORCE
 Disables device name enforcment.   It  will  cause  VDS  to
 behave  as it did prior to this enhancement.  CLEAR ENFORCE
 is the default condition when VDS is run under  control  of
 APT.  See HELP SET ENFORCE for an example.

 Format:
    CLEAR ENFORCE
2 EVENT
 Causes event flags to be cleared.   Some  programs  utilize
 event flags to specify non-standard program options.

 Format:
    CLEAR EVENT [FLAGS] arg-list
3 Parameters
 arg-list
   A list of event flag numbers, from decimal 1 to 23, to be
   cleared;  separated  by  commas.   Or, alternatively, the
   keyword "ALL" will clear all event flags.
2 FLAGS
 Causes the Supervisor control flags  to  be  cleared.   The
 "FLAGS" keyword is optional and may be omitted.

 Format:
    CLEAR [FLAGS] arg-list
3 Parameters
 arg-list
   A list of flag names to be cleared, separated by  commas.
   Type   "HELP  SPECIFY  FLAGS"  for  information  on  flag
   keywords and their significance.
1 CONTINUE
 Continue program execution from  where  it  was  halted  due  to
 halt-on-error or ^C interrupt.

 Format:
    CONTINUE
1 CONTROL-C
 Interrupts execution of Supervisor  or  diagnostic  program  and
 enters  Supervisor command wait state.  Execution can be resumed
 by CONTINUE or terminated by ABORT (ABORT has  no  effect  if  a
 Supervisor function was interrupted).

 Format:
    ^C
1 CRD
 The  CUSTOMER  RUNNABLE  DIAGNOSTIC  (CRD)  Package  is  a   VAX
 Diagnostic  Supervisor  supported  test  system  that  allows an
 inexperienced user the capability of verifying  proper  hardware
 operation  by  executing  VAX  Diagnostics.   It  provides quick
 isolation of failures to the subsystem level.

  o  Off-Line AUTOTEST

     VAX-11/730 supported and verifies the operation of CPU,  VMS
     system  disk,  and diagnostic load disk.  It is invoked ONLY
     IN CONSOLE  MODE  by  typing  "T"  to  the  Console  prompt.
     Successful completion initiates CRD Off-line Menu.  For more
     information type to Supervisor prompt "HELP ENSAB AUTO".

  o  Off-line MENU

     VAX-11/730  supported  and   verifies   operation   of   all
     subsystems  including  options.   The Menu format provides a
     simple  interface  to  select  and  test  one  or  all   VAX
     subsytems.  It is invoked in Console mode by typing "T/M" to
     the Console prompt, or in Supervisor mode by typing "CRD" to
     the  Supervisor  prompt.   For  more information type to the
     Supervisor prompt "HELP ENSAB MENU".

1 DEATTACH
 Reverses the effect of an ATTACH command.  The specified  device
 Ptable  is  deleted.   Since  Ptables  are linked in a tree-like
 fashion, the DEATTACH command, as  well  as  'de-attaching'  the
 specified  device,  will  de-attach  all devices which have been
 attached to the specified device.  For example,  if  the  device
 DW0  had  been  attached to the HUB, and devices DMA and TTA had
 been attached to  DW0,  and  devices  DMA0  and  TTA0  had  been
 attached     to     them     (respectively),     the     command
 'DEATTACH/ADAPTER=HUB DW0' would cause  deletion  of  DW0,  DMA,
 TTA,  DMA0,  and  TTA0.   A  message  will be typed out for each
 device  which  is  de-attached.   The  qualifier  '/ADAPTER'  is
 required, and may either precede or follow the device name.

 Format:
    DEATTACH/ADAPTER=link device
    [or]
    DEATTACH device /ADAPTER=link
2 Parameters
 device
   The generic name of the device to  be  de-attached.   All
   devices  which  are  linked  to  this device will also be
   de-attached.
2 Qualifiers
/ADAPTER=link
 This qualifier is required for the  DEATTACH  command.   It
 specifies  the generic name of te device to which parameter
 'device' is linked.  For example, if device DW0  is  to  be
 de-attached   from   link   HUB,   the   command  would  be
 'DEATTACH/ADAPTER=HUB DW0'.
1 DEPOSIT
 Modifies the contents of a memory address.  The  data  type  and
 radix are specified by qualifiers or by data radix control (type
 "HELP SPECIFY RADIX" for radix control information).

 Format:
    DEPOSIT [qualifiers] address data
2 Parameters
 address
   Memory address (physical address if memory management  is
   disabled,  or  virtual  address  if  memory management is
   enabled) at which to deposit  the  data  value.   Specify
   address in current radix.

   Or a  general  register  may  be  modified.   Type  "HELP
   SPECIFY REGISTER" for information.

   Or an internal processor register (IPR) may be  modified.
   Type "HELP SPECIFY IPR" for IPR definitions.

 data
   Value in current radix to be deposited at  the  specified
   address.
2 Qualifiers
/NEXT=n
 Deposit the data in the next n locations.  n is  a  decimal
 number.
/LONGWORD
 Alter a 4-byte data segment at address
/WORD
 Alter a 2-byte data segment at address
/BYTE
 Alter a 1-byte data segment at address
/HEXADECIMAL
 Set default radix for command to hexadecimal (base 16).
/DECIMAL
 Set default radix for command to decimal (base 10).
/OCTAL
 Set default radix for command to octal (base 8).
1 DESELECT
 Specify that a device previously selected for testing is not  to
 be  tested.   No  program  will  be allowed access to the device
 until it  is  SELECTed.   When  a  device  is  ATTACHed,  it  is
 deselected  by  default;  and a device must have been previously
 attached before it can be manually DESELECTed.

 Format:
    DESELECT [Qualifiers] device-list
2 Parameters
 device-list
   A  list  of  generic  device  names  to  be   deselected,
   separated by commas.  Or alternatively, the keyword "ALL"
   to deselect all devices.  Type "HELP SPECIFY DEVICE"  for
   device name syntax.
2 Qualifiers
/ADAPTER=name
 Limit the DESELECT command to only affect devices which are
 attached  to  the  device  with  generic  name 'name'.  For
 example,  the  command  'DESELECT/ADAPTER=HUB   ALL'   will
 deselect  only devices attached directly to HUB (e.g., DW0,
 KA0).  This does NOT include the link  device  itself,  nor
 any devices attached to the deselected devices.
1 Devices
 As well as the "device-independent" parameters required  by  the
 ATTACH  command  for  any  device,  most devices require device-
 dependent information.  Type "HELP DEVICE device-designator" for
 information on a specific device, or "HELP DEVICE..." for a list
 of all devices' requirements.  If the device is not listed here,
 it  is  known only within the diagnostic program(s) that use it;
 type "HELP program DEVICE" for information on  it  (e.g.,  "HELP
 EVRAA DEVICE").

 Device parameters include the legal range of  values  in  square
 brackets  (e.g.,  "[decimal  4-7]"  for  BR  level),  and device
 standard values in angle brackets (e.g., "<776750>" for the AA11
 CSR).
2 AA11K
 Description:   AA11K 4-channel digital to analog converter
 link:      DWn
 Generic name:  AAan
 Additional information:
    UNIBUS CSR [octal 760000-777776]<776750>
    UNIBUS vector [octal 2-776]<140>
    UNIBUS BR level [decimal 4-7]
 Tested by: EVALB, EVALF
2 AD11K
 Description:   AD11K 12-bit analog to digital converter
 link:      DWn
 Generic name:  ADan
 Additional information:
    UNIBUS CSR [octal 760000-777776]
    UNIBUS vector [octal 2-776]
    UNIBUS BR level [decimal 4-7]
 Tested by: EVALF, EVALC
2 CI750
 Description:   CI750 11/750 computer interconnect port
 link:      CMI
 Generic name:  PAan
 Additional information:
    SLOT number [decimal 10-15]
    BR level [decimal 4-7]
    Node number [decimal 0-255]
 Tested by: ECCGA, ECCGB, ECCGC, ECCGD, ECCGE
            EVGAA, EVGAB
2 CI780
 Description:   CI780 11/780 computer interconnect port
 link:      SBI
 Generic name:  PAan
 Additional information:
    TR number [decimal 1-15]
    BR level [decimal 4-7]
    Node number [decimal 0-255]
 Tested by: ESCGA, ESCGB, ESCGC, ESCGD, EVGAA, EVGAB
2 CI_NODE
 Description:   Device on the CI network
 link:      PAan
 Generic name:  name
 Additional information:
    Node_type [VAX780,VAX750,HSC50,KL10,CINT]
    Node_address [decimal 0-255]
 Tested by: None
2 CR11
 Description:   CR11 Card reader
 link:      DWn
 Generic name:  CRan
 Additional information:
    UNIBUS CSR [octal 760000-777776]<777160>
    UNIBUS vector [octal 2-776]<230>
    UNIBUS BR level [decimal 4-7]
 Tested by: EVABA
2 DISK
 Description:   HSC50 disk
 link:      name (CI_NODE generic name)
 Generic name:  name$DUan
 Tested by: None
2 DMC11
 Description:   DMC11 Synchronous single line interface
 link:      DWn
 Generic name:  XMan
 Additional information:
    UNIBUS CSR [octal 760000-777776]
    UNIBUS vector [octal 2-776]
    UNIBUS BR level [decimal 4-7]
 Tested by: EVDBA, EVDBB, ESDCA, EVDXA
2 DMF32A
 Description:   DMF32 Asynchronous Port
 link:      DWn
 Generic name:  TXan
 Tested by: EVDAC, EVDLC
2 DMF32P
 Description:   DMF32 Parallel Port
 link:      DWn
 Generic name:  LCa
 Tested by: EVDLD
2 DMF32S
 Description:   DMF32 Synchronous Port
 link:      DWn
 Generic name:  XGan
 Tested by: EVDLA, EVDLB
2 DMP11
 Description:   DMP11 Multi-drop comm. interface
 link:      DWn
 Generic name:  XDan
 Additional information:
    UNIBUS CSR [octal 760000-777776]
    UNIBUS vector [octal 2-776]
    UNIBUS BR level [decimal 4-7]
 Tested by: EVDBA, EVDMA, EVDMB, EVDXA
2 DMR11
 Description:   DMR11 Synchronous single line interface
 link:      DWn
 Generic name:  XMan
 Additional information:
    UNIBUS CSR [octal 760000-777776]
    UNIBUS vector [octal 2-776]
    UNIBUS BR level [decimal 4-7]
 Tested by: EVDMA, EVDXA
2 DN11
 Description:   DN11 Automatic calling unit interface
 link:      DWn
 Generic name:  DNan
 Additional information:
    UNIBUS CSR [octal 760000-777776]
    UNIBUS vector [octal 0-776]
    UNIBUS BR level [decimal 4-7]
    Y-OPTION [YES/NO]
    Z-OPTION [YES/NO]
 Tested by: EVDNB
2 DR11B
 Description:   DR11B General purpose DMA interface
 link:      DWn
 Generic name:  XBan
 Additional information:
    UNIBUS CSR [octal 760000-777776]<772410>
    UNIBUS vector [octal 2-776]<124>
    UNIBUS BR level [decimal 4-7]
 Tested by: ESDRA, EVDRE
2 DR11K
 Description:   DR11K General purpose parallel I/O interface
 link:      DWn
 Generic name:  XRan
 Additional information:
    UNIBUS CSR [octal 760000-777776]
    UNIBUS vector [octal 2-776]
    UNIBUS BR level [decimal 4-7]
 Tested by: EVALD, EVALF
2 DR11W
 Description:   DR11W General purpose DMA I/O interface
 link:      DWn
 Generic name:  XAan
 Additional information:
    UNIBUS CSR [octal 760000-777776]
    UNIBUS vector [octal 2-776]
    UNIBUS BR level [decimal 4-7]
 Tested by: EVDRB, EVDRE
2 DR750
 Description:   DR750 CMI parallel interface
 link:      HUB
 Generic name:  XFan
 Additional information:
    slot number [decimal 1-15]
    BR number [decimal 4-7]
    Self test [YES/NO]
    Test configuration [1CPU,2CPU]
    Test unit [YES/NO]
 Tested by: EVDFD, EVDFE, EVDFF, EVDFG, EVDFK
            ECDFA, ECDFB, ECDFK
2 DR780
 Description:   DR780 SBI parallel interface
 link:      HUB
 Generic name:  XFan
 Additional information:
    TR number [decimal 1-15]
    BR number [decimal 4-7]
    Self test [YES/NO]
    Test configuration [1CPU,2CPU]
    Test unit [YES/NO]
 Tested by: ESDFA, ESDFB, ESDFC, EVDFD, EVDFE,
            EVDFF, EVDFG, EVDFK
2 DUP11
 Description:   DUP11 Synchronous single line interface
 link:      DWn
 Generic name:  XWan
 Additional information:
    UNIBUS CSR [octal 760000-777776]
    UNIBUS vector [octal 2-776]
    UNIBUS BR level [decimal 4-7]
 Tested by: ESDCA, EVDUP, EVDUQ
2 DW730
 Description:   DW730 11/730 UNIBUS adapter
 link:      HUB
 Generic name:  DW0
 Tested by: micro-diagnostics only
2 DW750
 Description:   DW750 11/750 UNIBUS adapter
 link:      HUB
 Generic name:  DWn
 Tested by: ECCBA
2 DW780
 Description:   DW780 11/780 UNIBUS adapter
 link:      HUB
 Generic name:  DWn
 Additional information:
    TR number [decimal 1-15]<3>
    BR number [decimal 4-7]<5>
 Tested by: ESCBA
2 DZ11
 Description:   DZ11 Asynchronous multi-line communications interface
 link:      DWn
 Generic name:  TTa
 Additional information:
    UNIBUS CSR [octal 760000-777776]
    UNIBUS vector [octal 2-776]
    UNIBUS BR level [decimal 4-7]
    MODULE TYPE [EIA/20MA]
2 DZ32
 Description:   DZ32 Asynchronous multi-line communications interface
 link:      DWn
 Generic name:  TTa
 Additional information:
    UNIBUS CSR [octal 760000-777776]
    UNIBUS vector [octal 2-776]
    UNIBUS BR level [decimal 4-7]
 Tested by: EVDAB
2 IEU11A
  Description:   IEU11-A Dual IEC/IEEE Bus Controller
  link:         DWn
  Generic name:  IXa
  Additional information:
    UNIBUS Base [octal 760000-777760]
        UNIBUS vector [octal 0-774]
        UNIBUS BR level [decimal 4-7]
  Tested by:     EVCDB, EVCDC
2 KA730
 Description:   KA730 11/730 central processor
 link:      HUB
 Generic name:  KAn
 Additional information:
    Time-of-year clock? [Yes/No]
    WCS last address? [hex 0-FFFF]
    Accelerator type? [decimal 0-255]
    K-bytes of Main Memory? [decimal 0-5120]
    User WCS loaded? [Yes/No]
    SB errors? [Yes/No]
 Tested by: EVKAA, EVKAB, EVKAC, EVKAD, EVKAE,
        EVXBB, ENKAX
2 KA750
 Description:   KA750 11/750 central processor
 link:      HUB
 Generic name:  KAn
 Additional information:
    G-floating instructions? [Yes/No]
    H-floating instructions? [Yes/No]
    Time-of-year clock? [Yes/No]
    WCS last address? [hex 0-FFFF]
    Accelerator type? [decimal 0-255]
 Tested by: EVKAA, EVKAB, EVKAC, EVKAD, EVKAE,
        EVXBB, ECKAX
2 KA780
 Description:   KA780 11/780 central processor
 link:      HUB
 Generic name:  KAn
 Additional information:
    G-floating instructions? [Yes/No]
    H-floating instructions? [Yes/No]
    WCS last address? [hex 0-FFFF]
    Accelerator type? [decimal 0-255]
 Tested by: EVKAA, EVKAB, EVKAC, EVKAD, EVKAE,
        EVXBB
2 KMC11
 Description:   KMC11 Auxiliary Communications Processor
 link:      DWn
 Generic name:  XKan
 Additional information:
    UNIBUS CSR [octal 760000-777776]
    UNIBUS vector [octal 2-776]
    UNIBUS BR level [decimal 4-7]
 Tested by: EVDHA, EVDXA
2 KMS11
 Description:   KMS11 Data Communications Link
 link:      DWn
 Generic name:  YYa
 Additional information:
    UNIBUS CSR [octal 760000-777776]
    UNIBUS vector [octal 2-776]
    UNIBUS BR level [decimal 4-7]
    MODEMCSR   [octal 760000-777776]
 Tested by: EVDHA, EVDHB, EVDIA, EVDIB, EVDIE, EVDJA, EVDKA
2 KMSYG
 Description:   VAX to PDP11 communication link
 link:      DWn
 Generic name:  YGa
 Additional information:
    UNIBUS CSR [octal 760000-777776]
    UNIBUS vector [octal 2-776]
    UNIBUS BR level [decimal 4-7]
 Tested by: EVDMF
2 KW11K
 Description:   KW11K General purpose watchdog timer
 link:      DWn
 Generic name:  KWan
 Additional information:
    UNIBUS CSR [octal 760000-777776]
    UNIBUS vector [octal 2-776]
    UNIBUS BR level [decimal 4-7]
 Tested by: EVALE, EVALF
2 LA34
 Description:   LA34 DECwriter IV printing terminal
 link:      TTa
 Generic name:  TTan
 Tested by: EVTAA, EVTBA, EVXBA
2 LA36
 Description:   LA36 DECwriter II printing terminal
 link:      TTa
 Generic name:  TTan
 Tested by: EVTAA, EVTBA, EVXBA
2 LA38
 Description:   LA38
 link:      TTa
 Generic name:  TTan
 Tested by: EVTAA, EVTBA, EVXBA
2 LA120
 Description:   LA120 DECwriter III printing terminal
 link:      TTa
 Generic name:  TTan
 Tested by: EVTAA, EVTBA, EVXBA
2 LA180
 Description:   LA180 DECprinter I line printer
 link:      LPa
 Generic name:  LPan
 Tested by: EVAAA, EVXBA, EVXBB
2 LN01
 Description:   LN01 Laser line printer
 link:      LCa
 Generic name:  LCan
 Tested by: EVAAA
2 LP04
 Description:   LP04 Line printer
 link:      LPa
 Generic name:  LPan
 Tested by: EVAAA, EVXBA, EVXBB
2 LP05
 Description:   LP05 Line printer
 link:      LPa
 Generic name:  LPan
 Tested by: EVAAA, EVXBA, EVXBB
2 LP06
 Description:   LP06 Line printer
 link:      LPa
 Generic name:  LPan
 Tested by: EVAAA, EVXBA, EVXBB
2 LP11
 Description:   LP11 Line printer controller
 link:      DWn
 Generic name:  LPa
 Additional information:
    UNIBUS CSR [octal 760000-777776]<777514>
    UNIBUS vector [octal 2-776]<200>
    UNIBUS BR level [decimal 4-7]
 Tested by: EVAAA, EVXBA, EVXBB
2 LP14
 Description:   LP14 Line printer
 link:      LPa
 Generic name:  LPan
 Tested by: EVAAA, EVXBA, EVXBB
2 LP25
 Description:   LP25 Line printer (band)
 link:      LPa
 Generic name:  LPan
 Tested by: EVAAA
2 LPA11K
 Description:   LPA11K Laboratory subsystem controller
 link:      DWn
 Generic name:  LAan
 Additional information:
    UNIBUS CSR [octal 760000-777776]<770460>
    UNIBUS vector [octal 2-776]
    UNIBUS BR level [decimal 4-7]
 Tested by: EVALA, EVDXA
2 MA780
 Description:   MA780 11/780 Multi-port memory controller
 link:      HUB
 Generic name:  MAn
 Additional information:
    TR number [decimal 1-15]
    BR number [decimal 4-7]
    MPM [decimal 0-3]
    PORT [decimal 0-3]
 Tested by: ESCCA, EVXBB
2 MBE
 Description:   MBE Massbus exerciser
 link:      RHn
 Generic name:  MBan
 Additional information:
    drive [decimal 0-7]
 Tested by: ESCCA, EVXBA
2 ML11
 Description:   ML11 Solid state disk
 link:      RHn
 Generic name:  EMan
 Additional information:
    Array boards [decimal 1-16]
    Chip size [16K, 64K]
 Tested by: EVXBA, EVRAA, EVRAC, EVRBA, EVRCA,
            EVXBB
2 MS750
 Description:   MS750 11/750 memory controller
 link:      HUB
 Generic name:  MSn
 Additional information:
    BR number [decimal 4-7]
 Tested by: ECKAM, EVXBB
2 MS780
 Description:   MS780 11/780 memory controller
 link:      HUB
 Generic name:  MSn
 Additional information:
    TR number [decimal 1-15]
    Number of Arrays [decimal 0-16]
 Tested by: EVXBB
2 PCL11
 Description:   PCL11-B Parallel communications link
 link:      DWn
 Generic name:  XPn
 Additional information:
    UNIBUS CSR [octal 760000-777776]
    UNIBUS vector [octal 2-776]
    UNIBUS BR level [decimal 4-7]
 Tested by: EVDPC, EVDPD, EVDPE, ESDPA, ESDPB
2 R80
 Description:   R80 fixed media disk (IDC)
 link:      DQa
 Generic name:  DQan
 Tested by: EVRAA, EVRAD, ENRGA, ENRKA
2 RA60
 Description:   RA60 removable media SDI disk
 link:      DUa
 Generic name:  DJan
 Tested by: EVRLA, EVRLB
2 RA80
 Description:   RA80 fixed media SDI disk
 link:      DUa
 Generic name:  DUan
 Tested by: EVRLA, EVRLB
2 RA81
 Description:   RA81 fixed media SDI disk
 link:      DUa
 Generic name:  DUan
 Tested by: EVRLA, EVRLB
2 RB730
 Description:   Nebula IDC disk controller
 link:      HUB
 Generic name:  DQa
 Tested by: micro-diagnostics
2 RC11
 Description:   UNIBUS to disk controller
 link:      DWn
 Generic name:  DAa
 Additional information:
    IP (CSR) [octal 760000-777774]
    UNIBUS vector [octal 4-774]
    UNIBUS BR level [decimal 4-7]
 Tested by:
2 RC25
 Description:   RC25 removable media disk
 link:      DAa
 Generic name:  DAan
 Tested by: EVRMB, EVRMA
2 RCF25
 Description:   RCF25 fixed media disk
 link:      DAa
 Generic name:  DAan
 Tested by: EVRMB, EVRMA
2 RH750
 Description:   RH750 11/750 Massbus adapter
 link:      HUB
 Generic name:  RHn
 Additional information:
    BR number [decimal 4-7]<5>
 Tested by: ECCAA
2 RH780
 Description:   RH780 11/780 Massbus adapter
 link:      HUB
 Generic name:  RHn
 Additional information:
    TR number [decimal 1-15]<8_>
    BR level [decimal 4-7]<5>
 Tested by: ESCAA,
2 RK06
 Description:   RK06 disk drive
 link:      DMa
 Generic name:  DMan
 Tested by: EVXBA, EVRAA, EVRAC, EVRAD,
        EVREF, EVREG
2 RK07
 Description:   RK07 disk drive
 link:      DMa
 Generic name:  DMan
 Tested by: EVXBA, EVRAA, EVRAC, EVRAD,
        EVREF, EVREG
2 RK611
 Description:   RK06/07 controller
 link:      DWn
 Generic name:  DMa
 Additional information:
    UNIBUS CSR [octal 760000-777776]<777440>
    UNIBUS vector [octal 2-776]<210>
    UNIBUS BR level [decimal 4-7]<5>
 Tested by: EVREA, EVREB, EVREC, EVRED, EVREE
2 RL01
 Description:   RL01 disk drive
 link:      DLa
 Generic name:  DLan
 Tested by: ?
2 RL02
 Description:   RL02 disk drive
 link:      DLa (or DQa)
 Generic name:  DLan (or DQan)
 Tested by: EVRAA, EVRAD, EVRFA, EVXBB
2 RL11
 Description:   RL01/02 controller
 link:      DWn
 Generic name:  DLa
 Additional information:
    UNIBUS CSR [octal 760000-777776]<774400>
    UNIBUS vector [octal 2-776]<160>
    UNIBUS BR level [decimal 4-7]<5>
 Tested by: EVRFA
2 RM03
 Description:   RM03 disk drive
 link:      RHn
 Generic name:  DRan
 Tested by: EVXBA, EVRAA, EVRAC, EVRAD,
        EVRDA, EVRDB
2 RM05
 Description:   RM05 disk drive
 link:      RHn
 Generic name:  DRan
 Tested by: EVRAA, EVRAC, EVRAD, EVRDA,
        EVRDB
2 RM80
 Description:   RM80 disk drive
 link:      RHn
 Generic name:  DRan
 Tested by: EVRAA, EVRAD, EVRDA, EVRGA,
        EVRGB
2 RP04
 Description:   RP04 disk drive
 link:      RHn
 Generic name:  DBan
 Tested by: EVRAA, EVRAC, EVRAD, EVRBA,
        EVRCA, EVXBA, EVXBB
2 RP05
 Description:   RP05 disk drive
 link:      RHn
 Generic name:  DBan
 Tested by: EVRAA, EVRAC, EVRAD, EVRBA,
            EVRCA, EVXBA, EVXBB
2 RP06
 Description:   RP06 disk drive
 link:      RHn
 Generic name:  DBan
 Tested by: EVRAA, EVRAC, EVRAD, EVRBA,
            EVRCA, EVXBA, EVXBB
2 RP07
 Description:   RP07 disk drive
 link:      RHn
 Generic name:  DRan
 Tested by: EVRAA, EVRAD, EVRHA, EVRHB,
        EVRHC
2 RX02
 Description:   RX02 floppy drive
 link:      DYa
 Generic name:  DYan
 Tested by: EVRAA, EVRAC
2 RX211
 Description:   RX01/02 floppy controller
 link:      DWn
 Generic name:  DYa
 Additional information:
    UNIBUS CSR [octal 760000-777776]<777170>
    UNIBUS vector [octal 2-776]<264>
    UNIBUS BR level [decimal 4-7]<5>
 Tested by: EVRIA
2 TE16
 Description:   TE16 magtape drive
 link:      MTa
 Generic name:  MTan
 Tested by: EVMAA, EVMAB, EVMAC, EVXBA,
            EVXBB
2 TM03
 Description:   TM03 Tape subsystem controller/formatter
 link:      RHn
 Generic name:  MTa
 Additional information:
    drive number [decimal 0-7]
 Tested by: EVMAC
2 TM78
 Description:   TU78 tape subsystem controller
 link:      RHn
 Generic name:  MFa
 Additional information:
    drive number [decimal 0-7]
 Tested by: EVMAE
2 TS11
 Description:   TS11/TS04 tape subsystem
 link:      DWn
 Generic name:  MSa0
 Additional information:
    UNIBUS CSR [octal 760000-777776]<772520>
    UNIBUS vector [octal 2-776]<224>
    UNIBUS BR level [decimal 4-7]<5>
 Tested by: EVMAA, EVMAD, EVXBB
2 TU45
 Description:   TU45 magtape drive
 link:      MTa
 Generic name:  MTan
 Tested by: EVMAA, EVMAB, EVMAC, EVXBA,
            EVXBB
2 TU58
 Description:   TU58 DECtape II tape drive
 link:      DWn
 Generic name:  DDan
 Additional information:
    UNIBUS CSR [octal 760000-777776]<776500>
    UNIBUS vector [octal 2-776]
    UNIBUS BR level [decimal 4-7]
 Tested by: EVRAA
2 TU77
 Description:   TU77 magtape drive
 link:      MTa
 Generic name:  MTan
 Tested by: EVMAA, EVMAB, EVMAC, EVXBA,
            EVXBB
2 TU78
 Description:   TU78 tape drive
 link:      MFa
 Generic name:  MFan
 Tested by: EVMAA
2 TU80
 Description:   TU80 tape subsystem
 link:      DWn
 Generic name:  MSa0
 Additional information:
    UNIBUS CSR [octal 760000-777776]<772520>
    UNIBUS vector [octal 2-776]<224>
    UNIBUS BR level [decimal 4-7]<5>
 Tested by:
2 UBE
 Description:   UBE Unibus exerciser
 link:      DWn
 Generic name:  UBan
 Additional information:
    UNIBUS CSR [octal 760000-777776]
    UNIBUS vector [octal 2-776]
    UNIBUS BR level [decimal 4-7]
 Tested by: ECCBA, EVXBA, ESCCA
2 UDA50
 Description:   UNIBUS to SDI controller
 link:      DWn
 Generic name:  DUa
 Additional information:
    UDAIP (CSR) [octal 760000-777776]
    UNIBUS vector [octal 2-776]
    UNIBUS BR level [decimal 4-7]
    Burst Rate [decimal 0-63]
 Tested by: EVRLA
2 UNA11
 Description:   UNIBUS  to NI adapter
 link:      DWn
 Generic name:  XEan
 Additional information:
    UNIBUS CSR [octal 760000-777776]
    UNIBUS vector [octal 2-776]
    UNIBUS BR level [decimal 4-7]
 Tested by: EVDWA, EVDWB
2 VT50
 Description:   VT50 Video terminal
 link:      TTa
 Generic name:  TTan
 Tested by: EVTAA, EVTBA
2 VT52
 Description:   VT52 Video terminal
 link:      TTa
 Generic name:  TTan
 Tested by: EVTAA, EVTBA
2 VT55
 Description:   VT55 Video terminal
 link:      TTa
 Generic name:  TTan
 Tested by: EVTAA, EVTBA
2 VT100
 Description:   VT100 Video terminal
 link:      TTa
 Generic name:  TTan
 Additional information:
 Tested by: EVTAA, EVTBA
1 DIRECTORY
 Type out  a  list  of  files  which  match  the  specified  file
 specification  (type  HELP  SPECIFY FILE-SPEC for information on
 file specifications).   The  filename  and/or  filetype  can  be
 wildcarded  with  the "*" (matching any sequence of characters),
 or the "%" (matching  any  single  character)  characters.   The
 other  fields  (device,  directory,  and  version)  can  NOT  be
 wildcarded.  If filename or filetype  are  not  specified,  they
 default to "*".

 Format:
    DIRECTORY [qualifiers]
              [device:][[directory]]filename.filetype;version
2 Parameters
 device
   The device from which to type directory.  The device must
   have  been  previously  ATTACHed.   In user mode, it must
   also have been mounted under VMS.
 directory
   If the  device  is  directory  formatted,  specifies  the
   directory  to  list.  The directory name must be enclosed
   in brackets.  It can include subdirectories separated  by
   ".".

 The original default is the directory from which which  the
 Supervisor  was  loaded in standalone (either [SYSMAINT] Or
 [SYSx.SYSMAINT]  where  "x"  is  a  hex  digit);   or   the
 [SYSMAINT]  account  on the current SYS$DISK on-line.  Note
 that as a special case, if SYS$DISK translates to the  form
 "device:[.SYSx]"  where "x" is a hex digit, the VDS default
 will be "device:[SYSx.SYSMAINT]".

 Examples:
    DIRECTORY DMA0:[SYSMAINT]
    DIRECTORY MTA0:.EXE
    DIRECTORY [DS]E%SAA
    DIR/WIDE
2 Qualifiers
/WIDE
 Changes the directory display to  one  filename  per  line.
 This  switch should be used to display long filenames which
 would normally be truncated.
1 EXAMINE
 Displays the contents of  the  data  segment  at  the  specified
 address, in the current radix and data type.  Type "HELP SPECIFY
 RADIX" for radix information.

 Format:
    EXAMINE [qualifiers] address
2 Parameters
 address
   Memory address in  current  radix  (physical  address  if
   memory  management is disabled, virtual address if memory
   management is enabled).

   Alternatively, specify a  general  register  (type  "HELP
   SPECIFY   REGISTER"   for  information)  or  an  internal
   processor register (IPR) (type  "HELP  SPECIFY  IPR"  for
   information on IPR's).
2 Qualifiers
/NEXT=n
 Type the contents of the next  n  data  segments  from  the
 specified address.  n is a decimal number.
/LONGWORD
 examine a 4-byte data segment
/WORD
 examine a 2-byte data segment
/BYTE
 examine a 1-byte data segment
/HEXADECIMAL
 Type data segment in hexadecimal radix (base 16).
/DECIMAL
 Type data segment in decimal radix (base 10).
/OCTAL
 Type data segment in octal radix (base 8).
/ASCII
 Type data segment as ascii characters
1 EXIT
 This command causes the Supervisor to terminate.  In an  on-line
 mode  (under  VMS),  the  Supervisor will execute a $EXIT system
 service to return to DCL.  In standalone  mode,  the  Supervisor
 will  execute  a  HALT  instruction; typing the console CONTINUE
 command will resume Supervisor execution.

 Format:
    EXIT
1 HELP
 The Supervisor HELP command types out information regarding  the
 Supervisor  or  a diagnostic program.  After reading a specially
 formatted file from  the  default  load  device,  it  types  the
 information  for  the topic(s).  Help is obtained from EVSAA.HLP
 by default.  If a diagnostic program name is  specified  as  the
 topic, then help is extracted from the program-name.HLP file.

 The Supervisor HELP facility allows three types of  "wildcards".
 Type  HELP SPECIFY HELP for more information on both wildcarding
 and the allowable topic formats.

 Help can be obtained on a particular topic by typing:
    HELP topic subtopic subsubtopic (etc.)
1 INITPCS
 Reloads the 11/750 PCS with the patches contained  in  the  file
 PCS750.BIN  which  is found on the console TU58.  If the file is
 not found on the console TU58, the supervisor's onboard copy  of
 the patches are loaded into the PCS.  Note that the supervisor's
 onboard copy of patches are loaded into the  PCS  at  supervisor
 boot time.

 Format:
    INITPCS
1 LOAD
 Load a program image into memory from a device.

 Format:
    LOAD file-spec
2 Parameters
 file-spec
   File specification for the  file  to  be  loaded.   (Type
   "HELP    SPECIFY   FILE-SPEC"   for   details   on   file
   specification format).  The file type defaults to ".EXE".
1 NEXT
 Executes the next n single machine instructions starting at  the
 current   PC.    After   the  instruction(s)  is  executed,  the
 Supervisor will display the new PC and the next 4 bytes at  that
 address  (the  next  instruction opcode, plus operand specifiers
 and/or further opcodes).

 Use NEXT to step through a section of code where  a  problem  is
 suspected.

 You can not use NEXT unless the program has been  stopped  at  a
 breakpoint!

 Format:
    NEXT [n]
2 Parameters
 n
   decimal number of instructions to execute.   Defaults  to
   1.
1 QA
 The Diagnostic Supervisor has the  capability  to  automatically
 perform  specific  Quality  Assurance  (QA) checks on diagnostic
 programs.  One should read the "VAX Diagnostic Quality Assurance
 Checklist" for an explanation of the QA checks.

 Four Supervisor commands have been enhanced to affect  QA.   The
 RUN  and START commands cause QA to be performed on a diagnostic
 program.  The SET command allows one to control portions of  the
 QA  process  by  setting  certain  QA  default values.  The SHOW
 command allows one to see the current settings of these values.

 In the current implementation, four  QA  checks  are  performed.
 These  four are the Normal Start check, the Multiple Pass check,
 the Loop on Test check, and the Run Backwards check.  A QA error
 results  from  the  diagnostic  program  reporting  an  error or
 attempting to ask the operator for  input  when  the  no-default
 flag  has  been  used.   If  no  QA  errors  are  found  in  the
 aforementioned checks, QA will print an  overall  error  summary
 table  and  then  abort the diagnostic.  If a QA error is found,
 information will be printed  that  should  help  the  diagnostic
 engineer  find  out  why  QA  failed.   Also,  the overall error
 summary table is printed and the diagnostic is aborted.
2 RUN
 The RUN command can be used to  QA  a  diagnostic  program.
 The /QA qualifier causes the program to undergo a number of
 QA checks.
3 Qualifiers
/QA
 The /QA qualifier on the RUN command causes the  Supervisor
 to  automatically  QA  the  diagnostic  program.   QA  will
 execute until either a QA error is found or until  all  the
 QA checks have finished.

 The /PASSES, /TEST, and the /SUBTEST qualifiers are ignored
 if  the  /QA qualifier is used.  The /SECTION qualifier may
 be used to run QA on a particular section.
2 SET
 The SET command allows one to control, to a certain extent,
 the  QA process.  There are five QA "flags" that can be set
 to various values.  Only two of these flags have any effect
 in the current implementation.  The QAERRORPRINTS flag, the
 QASUBTESTLOOPS flag, and the  QACKLOOPLOOPS  flag  are  not
 currently  used  when  QAing a diagnostic, although the SET
 command will allow one to set these flags.

 Format:
    SET option [dec-value]
3 QACKLOOPLOOPS
 This QA flag controls the number of times that QA will
 cause  a $DS_CKLOOP Supervisor macro to be executed in
 the QA Error checks.

 Format:
    SET QACKLOOPLOOPS dec-value
4 Parameters
 dec-value
   The dec-value must be in the range of  2  to  32767.
   The  dec-value  must  be specified.  The default for
   the  QACKLOOPLOOPS  flag  is  2.   That   is,   each
   $DS_CKLOOP  macro  in the diagnostic program will be
   executed dec-value times.
3 QADEFAULTS
 This QA flag allows one to set all  the  QA  flags  to
 their  default values.  The default values for each of
 the QA flags are as follows:

        QACKLOOPLOOPS:    2
        QAERRORPRINTS:   10
        QAMULTIPLEPASS:  10
        QASUBTESTLOOPS: 100
        QATESTLOOPS:    100

 Format:
    SET QACKLOOPLOOPS
3 QAERRORPRINTS
 This QA flag controls the number of times that QA will
 print  a  specific  diagnostic error message in the QA
 Error checks.

 Format:
    SET QAERRORPRINTS dec-value
4 Parameters
 dec-value
   The dec-value must be in the range of  2  to  32767.
   The  dec-value  must  be specified.  The default for
   the  QAERRORPRINTS  flag  is  2.   That   is,   each
   $DS_ERRxxxx  macro in the diagnostic program will be
   executed dec-value times (where xxxx is  DEV,  HARD,
   SOFT, or SYS).
3 QAMULTIPLEPASS
 This QA flag controls the number of  passes  that  the
 diagnostic will execute in the QA Multiple Pass check.

 Format:
    SET QAMULTIPLEPASS dec-value
4 Parameters
 dec-value
   The dec-value must be in the range of  1  to  32767.
   The  dec-value  must  be specified.  The default for
   the QAMULTIPLEPASS flag is  10.   That  is,  in  the
   Multiple Pass check, the diagnostic will be executed
   as if dec-value PASSES had been requested.
3 QASUBTESTLOOPS
 This QA flag controls the number of  times  that  each
 subtest is executed in the QA Loop on Subtest check.

 Format:
    SET QASUBTESTLOOPS dec-value
4 Parameters
 dec-value
   The dec-value must be in the range of  1  to  32767.
   The  dec-value  must  be specified.  The default for
   the QASUBTESTLOOPS  flag  is  100.   That  is,  each
   subtest  in  the diagnostic program will be executed
   dec-value times.
3 QATESTLOOPS
 This QA flag controls the number of  times  that  each
 test  is executed in the QA Loop on Test check in this
 check.

 Format:
    SET QATESTLOOPS dec-value
4 Parameters
 dec-value
   The dec-value must be in the range of  1  to  32767.
   The  dec-value  must  be specified.  The default for
   the QATESTLOOPS flag is 100.  That is, each test  in
   the  diagnostic  program  will be executed dec-value
   times.
2 SHOW
 The SHOW command prints the  current  settings  of  the  QA
 flags.   There  are  five  QA  "flags"  that  can be set to
 various values.  Only two of these flags have any effect in
 the  current  implementation.   The QAERRORPRINTS flag, the
 QASUBTESTLOOPS flag, and the  QACKLOOPLOOPS  flag  are  not
 currently  used  when QAing a diagnostic, although the SHOW
 command will allow one to see the current settings of these
 flags.

 Format:
    SHOW option
3 QACKLOOPLOOPS
 This command will print the  current  setting  of  the
 QACKLOOPLOOPS  QA  flag.   The  value  of  the flag is
 printed in decimal radix.

 Format:
    SHOW QACKLOOPLOOPS
3 QADEFAULTS
 This command will print the default  settings  of  all
 the  QA  flags.   The  values  are  printed in decimal
 radix.  Note that  the  values  printed  are  not  the
 current settings of the flags.

 Format:
    SHOW QADEFAULTS
3 QAERRORPRINTS
 This command will print the  current  setting  of  the
 QAERRORPRINTS  QA  flag.   The  value  of  the flag is
 printed in decimal radix.

 Format:
    SHOW QAERRORPRINTS
3 QAMULTIPLEPASS
 This command will print the  current  setting  of  the
 QAMULTIPLEPASS  QA  flag.   The  value  of the flag is
 printed in decimal radix.

 Format:
    SHOW QAMULTIPLEPASS
3 QASUBTESTLOOPS
 This command will print the  current  setting  of  the
 QASUBTESTLOOPS  QA  flag.   The  value  of the flag is
 printed in decimal radix.

 Format:
    SHOW QASUBTESTLOOPS
3 QATESTLOOPS
 This command will print the  current  setting  of  the
 QATESTLOOPS QA flag.  The value of the flag is printed
 in decimal radix.

 Format:
    SHOW QATESTLOOPS
2 START
 The START command can be used to QA a  diagnostic  program.
 The /QA qualifier causes the program to undergo a number of
 QA checks.
3 Qualifiers
/QA
 The  /QA  qualifier  on  the  START  command   causes   the
 Supervisor   to   automatically  QA  the  currently  loaded
 diagnostic program.  QA will  execute  until  either  a  QA
 error is found or until all the QA checks have finished.

 The /PASSES, /TEST, and the /SUBTEST qualifiers are ignored
 if  the  /QA qualifier is used.  The /SECTION qualifier may
 be used to run QA on a particular section.
1 RUN
 Load a program  image  into  memory  from  a  device  and  cause
 execution  of  the  image,  by  passing  control  first  to  the
 program's initialization code and then sequentially to each test
 within the selected section.

 Format:
    RUN file-spec [qualifiers]
2 Parameters
 file-spec
   file specification  for  file  to  be  run.   Type  "HELP
   SPECIFY  FILE-SPEC"  for file specification details.  The
   file type defaults to ".EXE".
2 Qualifiers
/SECTION=section-name
 Select a program section to be executed.  This  must  be  a
 section   defined   by  the  program  (Type  "HELP  program
 SECTIONS" for information on the sections implemented by  a
 particular program).  If the SECTION qualifier is not used,
 the section named DEFAULT, which must  be  present  in  all
 programs,  is  executed.   Only  those tests defined by the
 programmer to be within the specified section are executed.

 Examples:
    RUN EVRAA/SECTION=SEEK
    RUN EVXBA /SEC:DEFAULT
/SUBTEST=num
/TEST=first[=last]
 The value first defines a test number, within the  selected
 section,  at  which  to  begin  program  testing.  No lower
 numbered tests will be execute.

 If the value last is also  used,  it  defines  the  highest
 number test to execute.

 Alternatively,  the  value  first  may   be   used   alone,
 specifying  only  the  starting  test  number.   If so, the
 /SUBTEST=num qualifier can be used (note that the  /SUBTEST
 qualifier otherwise is meaningless and should not be used).
 When this form is used, execution will begin at test first.
 If  the /SUBTEST qualifier was used, execution will proceed
 until subtest num is  encountered.   If  the  /PASSES=count
 qualifier is also used, the program will repeatedly loop on
 that one subtest until termination, once  the  subtest  has
 been  reached once.  If the /SUBTEST qualifier is not used,
 testing continues to the last test of the section.

 If the /TEST qualifier is not used, first  defaults  to  1,
 and  last  defaults  to  the  highest  test  number  in the
 selected section.

 The values first, last, and num are decimal numbers.
/PASSES=count
 After  program  execution,  as  defined  by  use  of  other
 qualifiers,  has  been  completed, count is decremented and
 execution continues; the  program  will  loop  through  the
 specified cycle count times.

 As a special case, if the count is zero, the  program  will
 loop indefinitely.

 If the /PASSES qualifier is not used, count defaults  to  1
 unless the SEARCH flag is set, in which case count defaults
 to  infinity.   Type  "HELP  SPECIFY  FLAGS   SEARCH"   for
 information on the SEARCH feature.
/QA
 Use of this qualifier  causes  the  diagnostic  program  to
 undergo  a  number of Quality Assurance checks.  Type 'HELP
 QA RUN /QA' for more information.
1 SCRIPT
 A script is an ascii file of  Supervisor  and/or  program  input
 lines,  each  line  prefixed  by the exact prompt which it is to
 answer (e.g., a command line to the Supervisor must  begin  with
 the  string "DS> ").  These lines will be interpreted and echoed
 at the console.  When a script file is completed, "@ <EOF>" will
 be  typed  to signify that control has passed out of the script.
 A script may invoke another script, and will continue  when  the
 script  it  invoked  has  completed.  When all scripts have been
 completed, control returns to  the  console.   If  a  script  is
 interrupted  by  typing  ^C, any active scripts are flushed, and
 can not be continued.   Scripts  are  loaded  into  memory  when
 invoked;  therefore  the  media  need  not remain on-line during
 execution of the script.

    Note that this is distinct from the use of a VMS script  file
 which  must  not  include  prompt  strings,  which  can  only be
 utilized in user mode, does require an on-line media,  and  will
 cause  termination of the Supervisor when it completes.  Also, a
 VMS command file must cause execution of the Supervisor, and can
 not be invoked from within the Supervisor.

 Format:
    @file-spec
2 Parameters
 file-spec
   The  filename  to  be  loaded  as  a  script.   The  file
   extension defaults to ".COM".
1 SELECT
 Specify  that  a  device  may  be  accessed  for  testing  by  a
 diagnostic  program.  A device must be ATTACHed before it can be
 selected.  When  a  device  is  ATTACHed  it  is  deselected  by
 default.   In  user  mode,  the  device will be allocated by the
 Supervisor if the device Ptable descriptor so specifies.

 Format:
    SELECT [Qualifiers] device-list
2 Parameters
 device-list
   A list of generic device names to be selected,  separated
   by commas.  Or alternatively, the keyword "ALL" to select
   all devices.
2 Qualifiers
/ADAPTER=name
 Limit the SELECT command to only affect devices  which  are
 attached  to  the  device  with  generic  name 'name'.  For
 example, the command 'SELECT/ADAPTER=HUB ALL'  will  select
 only  devices  attached  directly  to HUB (e.g., DW0, KA0).
 This does NOT include  the  link  device  itself,  nor  any
 devices attached to the selected devices.
1 SET
 Alters characteristics  of  the  Supervisor  and/or  program  by
 setting flags, default values, breakpoints, etc.

 Format:
    SET option
2 BASE
 Set a base value which will be added to all  address  input
 to  the  EXAMINE,  DEPOSIT  and  SET  or  CLEAR  BREAKPOINT
 commands.  This is useful for referencing location  offsets
 within a routine, loadable I/O driver, etc.

 Format:
    SET BASE offset
3 Parameters
 offset
   An address value in the current radix by which subsequent
   address-type input is modified.  The initial offset is 0.
   Type "SET BASE 0" to remove an offset once set.
2 BREAKPOINT
 Set  a  breakpoint  at  the  specified  address.    Program
 execution   will   be   interrupted  immediately  prior  to
 execution of the instruction at that address,  and  control
 passed to the Supervisor command wait state.

 Format:
    SET BREAKPOINT address
3 Parameters
 address
   An address value in the current radix at which to set the
   breakpoint.   The  address  is  affected  by the SET BASE
   command.
2 DEFAULT
 Alters the default data type and radix for the EXAMINE  and
 DEPOSIT commands.

 Format:
    SET DEFAULT arg-list
3 Parameters
 arg-list
   A radix and/or data type specifier.  If only one is used,
   the other is not affected.  If both are used, they may be
   in either order and must be  separated  by  commas.   The
   initial default is HEX and LONG.

    Radix:      HEXADECIMAL, DECIMAL, OCTAL
    Data type:  BYTE, WORD, LONG

   Example:
    SET DEFAULT DECIMAL, BYTE
2 ENFORCE
 Enables  device  name  enforcement.   It  is  the   default
 condition  when  VDS starts, EXCEPT when running under APT.
 WARNING% - Some old scripts or diagnostic programs may  not
 function with ENFORCE set.

 Format:
    SET ENFORCE

 Example:
    DS>SET ENFORCE
    DS>ATTACH RP06 HUB DB0
    ??  Error in controller part of name, format  should  be
 "DBan"
    Device name?
    ^C
    DS>CLEAR ENFORCE
    DS>ATTACH RP06 HUB DB0
    DS>SHOW DEVICE
    _DB0    RP06 HUB 00000000
2 EVENT
 Set event flag(s).  Some programs utilize  event  flags  as
 control flags for non-standard options.

 Format:
    SET EVENT [FLAGS] arg-list
3 Parameters
 arg-list
   A list of event flag numbers, from decimal 1 to 23, to be
   set;  separate them by commas.  Or, the keyword "ALL" may
   be used to set all event flags.

   Examples:
    SET EVENT 1,20
    SET EVENT FLAGS 3
    SET EVENT ALL
2 FLAGS
 Causes Supervisor control flags to  be  set.   The  "FLAGS"
 keyword is optional.

 Format:
    SET [FLAGS] arg-list
3 Parameters
 arg-list
   A list of flag names to  be  set,  separated  by  commas.
   Type  "HELP  SPECIFY FLAGS" for information on specifying
   flag keywords, and their significance.
2 LOAD
 Alter the default load device and/or directory.

 Format:
    SET LOAD [device:][[directory]]
3 Parameters
 device
   The device from which files are to be loaded.  The device
   must have been previously ATTACHed.
 directory
   If the  device  is  directory  formatted,  specifies  the
   directory to load files from.  The directory name must be
   enclosed in brackets.

 The original default is directory [SYSMAINT] on the  device
 from which the Supervisor was loaded.

 Example:
    SET LOAD DMA0:[SYSMAINT]
2 MM
 Turn processor memory management on or off.

 Format:
    SET MM state

 Examples:
    SET MM ON
    SET MM OFF
3 Parameters
 state
   Specify whether memory management is to be turned  ON  or
   OFF
2 MEMORY
 Change the amount of total physical memory available to the
 supervisor  and  diagnostic programs.  The command will not
 be accepted in user mode.

 Format:
    SET MEMORY n
3 Parameters
 n
   The unit of measurement for "n" is pages of memory.   The
   value  of  "n" must be greater than or equal to zero, but
   less than the last value specified  for  total  available
   physical  memory.  Total available physical memory may be
   reset to the actual available physical memory by using  a
   value  of  zero for "n".  A value greater than the actual
   available physical memory will be accepted but not used.
2 PAGE
 Set the terminal page size.  When the specified  number  of
 lines  have  been  printed,  output is stopped and the user
 must respond to a prompt in order to continue output.

 Format:
    SET PAGE n
3 Parameters
 n
   The number of lines which will be printed on the terminal
   before  the user is prompted for more.  The default value
   is zero, which indicates that no paging will be done.
2 QACKLOOPLOOPS
 Set  the  QACKLOOPLOOPS  QA  flag.   Type  'HELP   QA   SET
 QACKLOOPLOOPS' for more information.

 Format:
    SET QACKLOOPLOOPS dec-value
2 QADEFAULTS
 Set the QA flags to their default values.   Type  'HELP  QA
 SET QADEFAULTS' for more information.

 Format:
    SET QADEFAULTS
2 QAERRORPRINTS
 Set  the  QAERRORPRINTS  QA  flag.   Type  'HELP   QA   SET
 QAERRORPRINTS' for more information.

 Format:
    SET QAERRORPRINTS dec-value
2 QAMULTIPLEPASS
 Set  the  QAMULTIPLEPASS  QA  flag.   Type  'HELP  QA   SET
 QAMULTIPLEPASS' for more information.

 Format:
    SET QAMULTIPLEPASS dec-value
2 QASUBTESTLOOPS
 Set  the  QASUBTESTLOOPS  QA  flag.   Type  'HELP  QA   SET
 QASUBTESTLOOPS' for more information.

 Format:
    SET QASUBTESTLOOPS dec-value
2 QATESTLOOPS
 Set  the  QATESTLOOPS  QA  flag.    Type   'HELP   QA   SET
 QATESTLOOPS' for more information.

 Format:
    SET QATESTLOOPS dec-value
2 WIDTH
 Set the terminal width.  When the print  head  (or  cursor)
 reaches  the  column  number  set,  a  carriage  return and
 linefeed will be forced.

 Format:
    SET WIDTH n
3 Parameters
 n
   A number from 1 to 132 inclusive.  The  default  terminal
   width is 80.
1 SHOW
 Examine current value of flags, breakpoints, etc.

 Format:
    SHOW option
2 BASE
 Display the current BASE value (in hex).

 Format:
    SHOW BASE
2 BREAKPOINTS
 All breakpoints currently set will be displayed.

 Format:
    SHOW BREAKPOINTS
2 DEFAULT
 Show the current default values for radix and data type (as
 in the SET DEFAULT command).

 Format:
    SHOW DEFAULT
2 DEVICE
 List characteristics of  ATTACH-ed  devices.   The  display
 format is:

    generic device-type link HUB-addr device-specific

 Example output:

 _TTA   DZ11    _DW0 6013E050 CSR=00000760120(O) -
                 VECTOR=00000000000(O) BR=4.

 Format:
    SHOW [Qualifiers] DEVICE [Qualifiers] [arg-list]
3 Parameters
 arg-list
   List of device generic names to be  displayed,  separated
   by  commas.   If no parameters are given, all devices are
   displayed.

   Examples:
    SHOW DEVICE
    SHOW DEV DMA0, LPA0:, DLA0
3 Qualifiers
/ADAPTER=name
 Limit the scope of the SHOW DEVICE command to devices which
 are  attached  to  the  device  'name'.   If no arg-list is
 given, all devices attached to the named device are listed;
 if  arg-list  is given, the named devices will be displayed
 only if they are attached to the specified  adapter.   This
 allows  devices  with  identical  names,  but  on different
 adapters, to co-exist (e.g., multiple  DECnet  paths  to  a
 given node).
/BRIEF
 Type  only  the  name  of  each  device,  rather  than  all
 parameters.
2 EVENT
 Show state of event flags.  Those flags currently  set  are
 listed.

 Format:
    SHOW EVENT [FLAGS]
2 FLAGS
 Show current state of control flags.   Both  currently  set
 and  currently  clear  flags  are  displayed.   Type  "HELP
 SPECIFY FLAGS" for description of control flags.

 Format:
    SHOW FLAGS
2 LOAD
 Display current default load device and directory.

 Format:
    SHOW LOAD
2 MEMORY
 Show current memory map.  Shows the  addresses  of  various
 important   sections   of  the  Diagnostic  Supervisor  and
 diagnostic, as well as physical memory size.

 Format:
    SHOW MEMORY [/Qualifiers]
3 Qualifiers
/ALL
 Combines the effects of /MAP, /DATA_STRUCTURE, and /BUFFER
/BUFFER
 Shows  the  size  and  location  of  memory  available  for
 diagnostic  buffers  (through  $DS_GETBUF  service).   Only
 meaningfull if a diagnostic is  loaded.   In  on-line  mode
 (under  VMS),  only  the  buffer space below the Diagnostic
 Supervisor is shown.
/DATA_STRUCTURE
 This qualifier causes listing of internal data  structures,
 including  SCB,  Page  tables,  etc.   Most of this data is
 shown only in standalone mode.
/MAP
 This qualifier is the default if no qualifiers are present.
 It  causes the Diagnostic Supervisor to list only the major
 components of  the  diagnostic  system,  and  the  physical
 memory size if system is standalone.
2 MM
 Show current state of memory management (on or off).

 Format:
    SHOW MM
2 PAGE
 Show current terminal page size.

 Format:
    SHOW PAGE
2 QACKLOOPLOOPS
 Show the current setting  of  the  QACKLOOPLOOPS  QA  flag.
 Type 'HELP QA SHOW QACKLOOPLOOPS' for more information.

 Format:
    SHOW QACKLOOPLOOPS
2 QADEFAULTS
 Show the default  settings  (not  necessarily  the  current
 settings)  of the QA flags.  Type 'HELP QA SHOW QADEFAULTS'
 for more information.

 Format:
    SHOW QADEFAULTS
2 QAERRORPRINTS
 Show the current setting  of  the  QAERRORPRINTS  QA  flag.
 Type 'HELP QA SHOW QAERRORPRINTS' for more information.

 Format:
    SHOW QAERRORPRINTS
2 QAMULTIPLEPASS
 Show the current setting of  the  QAMULTIPLEPASS  QA  flag.
 Type 'HELP QA SHOW QAMULTIPLEPASS' for more information.

 Format:
    SHOW QAMULTIPLEPASS
2 QASUBTESTLOOPS
 Show the current setting of  the  QASUBTESTLOOPS  QA  flag.
 Type 'HELP QA SHOW QASUBTESTLOOPS' for more information.

 Format:
    SHOW QASUBTESTLOOPS
2 QATESTLOOPS
 Show the current setting of the QATESTLOOPS QA flag.   Type
 'HELP QA SHOW QATESTLOOPS' for more information.

 Format:
    SHOW QATESTLOOPS
2 SECTIONS
 Display the section names supported by the currently loaded
 diagnostic.  If no diagnostic is loaded, a message is typed
 to that effect.

 Format:
    SHOW SECTIONS
2 SELECTED
 List the characteristics of all currently selected devices.
 The display format is:

    generic device-type link HUB-adr device-specific

 Format:
    SHOW [Qualifiers] SELECTED [Qualifiers]
3 Qualifiers
/BRIEF
 Type  only  the  name  of  each  device,  rather  than  all
 parameters.
2 STATUS
 Show the status of the running diagnostic (current section,
 pass,  test,  subtest,  time,  error count, and PC).  If no
 diagnostic is running, a message  will  be  typed  to  that
 effect.   This  command  may  be  used when a diagnostic is
 Control-C'd to check test progression; the  diagnostic  may
 then be CONTINUE'd.

 Format:
    SHOW STATUS
2 SUPPORT
 List the device types supported  by  the  currently  loaded
 diagnostic.   If no diagnostic is loaded, a message will be
 typed to that effect.

 Format:
    SHOW SUPPORT
2 WIDTH
 Show current terminal width setting.

 Format:
    SHOW WIDTH
1 Specify
2 Device
 A device name has the general format "GGan", where "GG"  is
 a  two  alphabetic  character string generally derived from
 the hardware designation.  "a" is an  alphabetic  character
 denoting the controller number, and "n" is a decimal number
 from 0 to 255, specifying  which  unit  number  the  device
 responds  to  on  it's  controller.   "a" and/or "n" may be
 used, when appropriate for the device.   Devices  which  do
 not  have  controllers  as  such  will use "n", for devices
 attached directly to the main bus (e.g., RH0, MS0, KA0), or
 "an"  where  "a"  is  arbitrary,  for devices at subsidiary
 levels (e.g., XMA0).
2 File-Spec
 File specifications have the format:

    device:[directory]filename.filetype;version

 The punctuation marks and brackets are required to separate
 the  fields.   All  but  filename  may  be omitted to allow
 default values.

     field       contents        syntax          default
     -----       --------------  -------         -------
     device      device name     GGan:           (last SET LOAD)
     directory   directory name  [directory]     (last SET LOAD)
     filename    file name       filename        none
     filetype    file type       .type           command-dependent
     version     file version    ;n              highest numbered

                            NOTE

     The directory field may include subdirectories,  in
     the form [directory.subdirectory.subdirectory...].

2 Flags
 Supervisor flags are represented by keywords.  For the  SET
 and  CLEAR FLAGS commands, any keywords may be used, or the
 additional keyword "ALL".  "ALL"  will  set  or  clear  all
 control  flags  except  SEARCH  and  BINARY,  which must be
 controlled individually.
3 BELL
 Bell  on  error.   When  set,  this  flag  will  cause  the
 Supervisor  to  transmit  a bell character (ASCII 7) to the
 console whenever the program detects an error.
3 BINARY
 When this flag is set,  each  message  (including  prompts)
 output  by  the  Supervisor will begin with a one byte type
 code field.  This type code will specify the class  of  the
 message  (e.g.,  ERRHARD, ERRSYS, command error, etc.).  It
 should not be set by human operators, and is intended  only
 for  use  by programs such as EVXBB which interact directly
 with the Supervisor.
3 HALT
 Halt on error.  When a program detects an error and if this
 flag is set, the Supervisor enters command wait state after
 all error messages associated with the failure  (and  which
 are  enabled)  have  been  output.   The  operator may then
 CONTINUE, ABORT, or START.  This flag has  precedence  over
 LOOP.
3 IE1
 Inhibit error messages at level 1.   When  set,  this  flag
 supresses  all error messages except those specially forced
 by the program or by the Supervisor via a $DS_PRINTF call.
3 IE2
 Inhibit error messages at level 2.   When  set,  this  flag
 supresses  basic  and  extended  information concerning the
 failure.  Only the first 3 lines (header)  of  the  message
 are typed for each failure.
3 IE3
 Inhibit error messages at level 3.   When  set,  this  flag
 supresses extended information concerning the failure.  The
 header and basic information messages are  typed  for  each
 failure.
3 IES
 Inhibit summary report.   When  set,  this  flag  supresses
 statistical report messages.
3 LOOP
 Loop on error.  When set, this flag causes the  program  to
 enter a predetermined scope loop on a test or subtest which
 detects a failure.  Set  the  IE1  flag  to  inhibit  error
 messages, thus speeding up the loop.  Looping will continue
 until the operator returns control to the Supervisor with a
 ^C command.  The operator may then CONTINUE with or without
 first clearing the LOOP flag; or ABORT the program.
3 OPERATOR
 Operator present.  When set, this flag informs the  program
 that  tests  requiring human intervention can be performed.
 When this flag is clear, programs will avoid such tests.
3 PROMPT
 Display long dialogue.  When set, this  flag  indicates  to
 the  Supervisor  that  the operator wants to see the limits
 and defaults for all questions asked by the program.
3 QUICK
 Quick verify.  When set, this flag indicates to the program
 that  the  operator wants a quick verify mode of operation.
 The  interpretation  of  this  flag  is  dependent  on  the
 program.    Type  "HELP  program  QUICK"  for  a  program's
 interpretation of QUICK.
3 SEARCH
 Enable error search  mode.   When  set,  this  flag  causes
 automatic  test  limit  modification.   When  an  error  is
 reported by a test, the upper test  limit  is  set  to  the
 previous  test.  With an "infinite" pass count (the default
 when the SEARCH  flag  is  set),  the  testing  cycle  will
 eventually be reduced to include only those lowest numbered
 tests which do not fail; providing device exerciser at  the
 highest level of functionality.
3 TRACE
 Report the execution of each test.   When  set,  this  flag
 causes the Supervisor to print the number and title of each
 test before dispatching control to the test.
3 VERIFY
 When this flag is set, commands and prompts  within  SCRIPT
 files  will  be echoed to the output console or file.  This
 is analogous to the VMS 'SET  VERIFY'  and  'SET  NOVERIFY'
 commands.   It  does  not  affect  command  read from a VMS
 script,  only  commands  within  a  file  passed   to   the
 Supervisor  via  an  '@  filespec'  command.   This flag is
 cleared by default.
2 Help
 Help can be obtained on a particular topic by typing:

    HELP topic subtopic subsubtopic (etc.)

 For information on specifying topics  and  subtopics,  type
 HELP SPECIFY HELP TOPICS_AND_SUBTOPICS.

 The Supervisor  HELP  command  supports  "wildcards".   The
 wildcards supported by the Supervisor include "*", "%", and
 "...".   Type  HELP  SPECIFY  HELP   WILDCARDS   for   more
 information.

 Type  HELP  SPECIFY  ABBREVIATIONS  for   help   on   using
 abbreviations for the topics and subtopics.
3 Abbreviations
 Abbreviations (which do not include wildcarded  characters)
 result  in  all  matches being displayed.  For example, the
 following two commands are equivalent:

    HELP S
    HELP S*

 For information on one specific topic (subtopic), the topic
 (subtopic)  may  be  abbreviated  to  the  least  number of
 characters that distinguishes that  topic  (subtopic)  from
 another.
3 Examples

 Below are some examples of Supervisor HELP commands:

    HELP
    HELP ATTACH *
    HELP EVRAA DEVICE ...
    HELP EXA
    HELP DEVICE LP1%
    HELP S*
    HELP SPECIFY ...
    HELP SPECIFY HELP EXAMPLES
3 Topics_And_Subtopics
 A topic can have the following formats:
 1)  An alphanumeric string (e.g., a command name, option)
 2)  An alphanumeric string preceded by a  "/"  (interpreted
     as a qualifier)
 3)  As in 1) or 2), with embedded "*" or "%" to  specify  a
     wildcarded topic
 4)  Any  of  the  above  followed  by  "...",  causing  all
     remaining topic levels to act as if they were "*".
 5)  The first topic may be a diagnostic  program  name,  in
     which  case  all  following  topic  keys  are  promoted
     (subtopic  becomes  topic,  etc.)  and  help  text   is
     extracted from the appropriate diagnostic help file.

3 Wildcards
 A topic or subtopic  can  contain  the  following  embedded
 wildcard characters:
  o  "*" matches anything
  o  "A*" matches all words beginning with "A"
  o  "*A" matches all words ending with "A"
  o  "A*A" matches all words beginning and ending with "A"
  o  "*A*" matches all words containing an "A"
  o  "A%C" matches any 3-character word beginning  with  "A"
     and ending with "C"


 In addition, a topic (subtopic) followed  by  "..."  causes
 all  remaining  topic  (subtopic)  levels to act as if they
 were "*".
2 IPR
 Internal Processor Registers (IPRs) can only be accessed in
 standalone  mode,  as  use of privileged instructions (MFPR
 and MTPR) is required.  They are specified by the character
 "P"  suffixed  by a number in the current radix.  Note as a
 special case that IPR C (hex) cannot be  accessed  by  "PC"
 which  would  refer  to  general  register  15,  but may be
 accessed as "P12" decimal, or as "P0C" or "P%XC"  to  force
 hexadecimal  interpretation  (Type "HELP SPECIFY RADIX" for
 more radix control information).
3 Mnemonics-definitions
 Register name           mnemonic dec hex access processor
 ----------------------  -------- --- --- ------ ------------
 Kernel stack pointer      KSP     0   0   R/W   all
 Executive stack pointer   ESP     1   1   R/W   all
 Supervisor stack pointer  SSP     2   2   R/W   all
 User stack pointer        USP     3   3   R/W   all
 Interrupt stack pointer   ISP     4   4   R/W   all
 P0 Base Register          P0BR    8   8   R/W   all
 P0 Length Register        P0LR    9   9   R/W   all
 P1 Base Register          P1BR   10   A   R/W   all
 P1 Length Register        P1LR   11   B   R/W   all
 System Base Register      SBR    12   C   R/W   all
 System Limit Register     SLR    13   D   R/W   all
 Process Control Blk Base  PCBB   16  10   R/W   all
 System Control Blk Base   SCBB   17  11   R/W   all
 Interrupt Priority Level  IPL    18  12   R/W   all
 AST Level                 ASTLVL 19  13   R/W   all
 Sftware Interrupt Request SIRR   20  14    W    all
 Sftware Interrupt Summary SISR   21  15   R/W   all
 Machine Check Status      MCSR   23  17    R    750
 Interval Clock Control    ICCS   24  18   R/W   all
 Next Interval Count       NICR   25  19    W    all
 Interval Count            ICR    26  1A    R    all
 Time Of Year              TODR   27  1B   R/W   all (option)
 Console Receiver C/S      RXCS   32  20   R/W   all
 Console Receiver D/B      RXDB   33  21    R    all
 Console Transmit C/S      TXCS   34  22   R/W   all
 Console Transmit D/B      TXDB   35  23    W    all
 Trnsltn Buffr Grp Disable TBDR   36  24   R/W   750
 Cache Disable             CADR   37  25   R/W   750
 Machine Chk Error Summary MCESR  38  26   R/W   750
 Cache Error               CAER   39  27   R/W   750
 Accelerator C/S           ACCS   40  28   R/W   780
 Accelerator Maintenance   ACCR   41  29   R/W   780
 WCS address               WCSA   44  2C   R/W   780
 WCS data                  WCSD   45  2D   R/W   780
 SBI Fault/Status          SBIFS  48  30   R/W   780
 SBI Silo                  SBIS   49  31    R    780
 SBI Silo Comparator       SBISC  50  32   R/W   780
 SBI Maintenance           SBIMT  51  33   R/W   780
 SBI Error Register        SBIER  52  34   R/W   780
 SBI Timeout Address       SBITA  53  35    R    780
 SBI Quadword Clear        SBIQC  54  36    W    780
 Memory Management Enable  MAPEN  56  38   R/W   all
 Trans. Buf. Inv. All      TBIA   57  39    W    all
 Trans. Buf. Inv. Single   TBIS   58  3A    W    all
 Translation Buffer        TB     59  3B   R/W   750
 Micro Program Breakpoint  MBRK   60  3C   R/W   780
 Performance Monitor Enb.  PMR    61  3D   R/W   all
 System Identification     SID    62  3E    R    all
2 Radix
 Most numeric values and  addresses  may  be  input  in  any
 convenient  radix,  except  where  specified  (e.g., UNIBUS
 device CSR and vector addresses are always octal, TR and BR
 numbers are always decimal).

 For the EXAMINE and  DEPOSIT  commands,  permanent  default
 radix  may  be  set  with  the  SET DEFAULT command, or the
 default for a single command may be set using qualifiers.

 More generally, a radix may be  specified  by  prefixing  a
 number with a radix specifier:
    %Xn causes n to be interpreted as hexadecimal
    %Dn causes n to be interpreted as decimal
    %On causes n to be interpreted as octal

 Examples:
    %O100   = octal 100
    %X4F    = hexadecimal 4F
    %D80    = decimal 80
2 Register
 General registers are specified by  appending  the  decimal
 register  number  (0  to 15) to the character "R".  Or, R15
 may be specified as "PC", R14 as "SP", R13 as "FP", and R12
 as "AP".
1 START
 Execute an image previously loaded either by the LOAD command or
 by a previous RUN command.  Execute the image by passing control
 first to the program's initialization code and then sequentially
 to each test within the selected section.

 Format:
    START [qualifiers]
2 Qualifiers
/SECTION=section-name
 Select a program section to be executed.  This  must  be  a
 section   defined   by  the  program  (Type  "HELP  program
 SECTIONS" for information on the sections implemented by  a
 particular program).  If the SECTION qualifier is not used,
 the section named DEFAULT, which must  be  present  in  all
 programs,  is  executed.   Only  those tests defined by the
 programmer to be within the specified section are executed.

 Examples:
    START /SECTION=SEEK
    START /SEC:DEFAULT
/SUBTEST=num
/TEST=first[=last]
 The value first defines a test number, within the  selected
 section,  at  which  to  begin  program  testing.  No lower
 numbered tests will be execute.

 If the value last is also  used,  it  defines  the  highest
 number test to execute.

 Alternatively,  the  value  first  may   be   used   alone,
 specifying  only  the  starting  test  number.   If so, the
 /SUBTEST=num qualifier can be used (note that the  /SUBTEST
 qualifier otherwise is meaningless and should not be used).
 When this form is used, execution will begin at test first.
 If  the /SUBTEST qualifier was used, execution will proceed
 until subtest num is  encountered.   If  the  /PASSES=count
 qualifier is also used, the program will repeatedly loop on
 that one subtest until termination, once  the  subtest  has
 been  reached once.  If the /SUBTEST qualifier is not used,
 testing continues to the last test of the section.

 If the /TEST qualifier is not used, first  defaults  to  1,
 and  last  defaults  to  the  highest  test  number  in the
 selected section.

 The values first, last, and num are decimal numbers.
/PASSES=count
 After  program  execution,  as  defined  by  use  of  other
 qualifiers,  has  been  completed, count is decremented and
 execution continues; the  program  will  loop  through  the
 specified cycle count times.

 As a special case, if the count is zero, the  program  will
 loop indefinitely.

 If the /PASSES qualifier is not used, count defaults  to  1
 unless the SEARCH flag is set, in which case count defaults
 to  infinity.   Type  "HELP  SPECIFY  FLAGS   SEARCH"   for
 information on the SEARCH feature.
/QA
 Use  of  this  qualifier  causes   the   currently   loaded
 diagnostic to undergo a number of Quality Assurance checks.
 Type 'HELP QA START /QA' for more information.
1 SUMMARY
 Dispatch control to the program's summary-generating code.   The
 effects  of  this  command  are  program-dependent.   Type "HELP
 program SUMMARY" for information on the summary of a  particular
 program.

 Format:
    SUMMARY
 
$ 
 
$ 
 
$ 
 
$ dism dua1:
 
$ 
Simulation stopped, PC: 80007B06 (BRB 80007B06)
sim> att rq1 bl-t941c-de.img
sim> c
mou/over=id dua1:
 
%MOUNT-I-MOUNTED, UVAXDIAG_3   mounted on _DUA1:
 
$ dir dua1:<sys0.sysmaint>

Directory DUA1:<SYS0.SYSMAINT>

EHXDH.EXE;1         EHXDH.HLP;1         EHXVS.EXE;1         EHXVS.HLP;1
EVRMA.EXE;1         EVRMA.HLP;1         EVRMB.EXE;1         EVRMB.HLP;1
EVRMC.EXE;1         EVRMC.HLP;1         

Total of 10 files.
 
$ type DUA1:<SYS0.SYSMAINT>*.hlp

DUA1:<SYS0.SYSMAINT>EHXDH.HLP;1
===============================
1 HELP
   
     The DHV11 is an asynchronous multiplexer  that  provides  an
 interface between eight asynchronous serial data communications
 channels and any processor that supports Q 22 bus devices.
 
     EHXDH is the name of the MICRO VAX Standalone Diagnostic.   It  is
 to  be  used to verify that a DHV11 connected via Q 22 bus to a MICRO VAX
 system  is  functioning  correctly.   

1 RUN_TIME

   EHXDH takes a little over 4 minutes to run.

1 REQUIREMENTS


2 HARDWARE 
   
      o  MICRO VAX 1 family processor with a Q 22 bus configured in the
         system

      o  console terminal

      o  enough  memory  is  already  available  on  any   system
         configuration

      o  1 to 8 DHV11s
      
2 HARDCORE

      o  whole system up to but not including DHV11 should be in proper
    working order.

2 SOFTWARE 

     1.  the MICRO VAX Diagnostic Supervisor (VDS) 

          -  EHSAA.EXE - 


     2.  EHXDH.EXE - this diagnostic

     3.  EVSAA.HLP - VDS help file

     4.  EHXDH.HLP -  the  help  file  used  with  the  VDS  help
         facility

1 PREREQUISITES

   - Hardcore fully tested

1 ATTACH_DHV11

   The following is an example of how to attach the device to
   be tested, and to load and run EHXDH:


   DIAGNOSTIC SUPERVISOR.  ZZ-EHSAA-Y6.13-510   27-JAN-1984 12:00:00.00
   DS> LOAD EHXDH       ; Load the DHV11 diagnostic
   DS> ATT DHV11        ; Attach the DHV11
   DEVICE LINK? HUB     ; The option is linked to the UBA
   DEVICE NAME? TXA     ; The option named unit: 
               ; (range=A-F)
   CSR? 770000       ; The CSR address: 
               ; (range=760000-777776)
   VECTOR?  300         ; Vector address: (range=0-776)
   BR? 5          ; BR Interrupt Level: (range=4-7)

   DS> SEL TXA:         ; Select Unit Under Test    
   
   DS> START         ; Start diagnostic execution
   
      The program should now be running.
1 OPTIONS

2 LINES_TO_TEST

   The following line will be displayed:

   Lines to test [(ALL), 0,1,2,...7]

   Various responses can be given:

   ALL - Test all lines 0 - 7 in ascending order,  default on <cr>.
   n   - Any line number.
   n,m - Any combination of line numbers,  i.e  0,3,7,1.
         They will be tested in the sequence entered.

   Any invalid entry will display an error message:

   ?? Invalid response

   Followed by a reprompt of the input request.

2 BAUD_RATE

   The following line will be displayed:

   Baud Rate [(4800),50,75,110,134.5,150,300,600,1200,1800,2400 
   7200,9600,19200,38400]

   Various responses can be given:

   n - Value, or <cr> default speed of 4800.

   Any invalid entry will display an error message:

   ?? Invalid response

   Followed by a reprompt of the input request.

2 LOOP_TYPE

   The following line will be displayed:

   Loop Type [(INTERNAL), EXTERNAL, STAGGERED, ]

   Various responses can be given:

   INTERNAL - Internal loopback will be used in the test, default on <cr>.
   EXTERNAL - External loopback connect is to be used.
   STAGGERED - Staggered loopbacj connector

   Any invalid entry will display an error message:

   ?? Invalid response

   Followed by a reprompt of the input request.

   
1 EVENT_FLAGS

   o  event flag 1 - turns of Rom Version reporting

1 SUMMARY

   Not implemented

1 DEVICE

   The DHV11 option is an asynchronous multiplexer which  provides  8
   full-duplex  asynchronous  serial  data channels on Q 22 bus systems.
   The option can be used in many applications.   These  include  data
   concentration,  terminal interfacing,  and cluster controlling.

2 FEATURES

   o   Eight full duplex asynchronous data channels.
   
   o   Large 256-entry First-In-First-Out,  (FIFO),  buffer for
       received characters, dataset status changes,  and
       diagnostic information.

   o   RS-423-A/V.10/X.26 and RS-232-C/V.28 compatible.

   o   Full-duplex point-to-point or auto-answer dial-up operation.

   o   Programmable split speed per line.

   o   Total module throughput of 15000 characters per second.

   o   Automatic flow control of transmitted and received data.

   o   Self-test and background monitor diagnostics.

   o   Programmable test facilities.   

   o   All  functions  are  programmable,  except for device
       address and vector selection,  which are made by hardware
       switches on the module.

   Enough modem control is provided on all 16 channels to allow
   auto-answer dial-up operation over the Public Switched Telephone
   Network,  (PSTN).   Suitable modems to use this facility are the Bell
   models 103,  113,  212,  or equivalent.   The DHV11 can also be used
   for point-to-point operation over private lines.   Modem control  is
   imlemented by software in the host.

   By using microcomputers the DHV11 releases the host system from many
   of the data handling tasks.

   One 8051 microcomputer controls NPR transmissions from the host
   system to the DHV11.   A second 8051 controls eight SC2681 Dual
   Universal Asynchronous Receiver Transmitters,  (DUARTs),  which carry
   out the serial/parallel and parallel/serial conversion of data.

   The DHV11 carries ROM-based diagnostics which are executed
   independently of the host.   A full range of diagnostic programs is
   also available for both PDP-11 and VAX-11 systems.

   A green LED gives the GO/NO-GO status of the module.   More detailed
   diagnostic information is also made available to the host system
   via the received character FIFO.   Loopback test connectors,  built
   into each line distribution panel,  are available for use with the
   system-based diagnostics.

   I/O addresses,  interrupt vectors,  and interrupt priority for the
   module are selected on three Dual-In-Line,  (DIL),  switchpacks.   All
   other DHV11 functions and configurations are programmable.

   To prevent data loss at high throughput levels,  the DHV11 can be
   programmed for automatic X-ON and X-OFF operation.

2 PHYSICAL

   o   One 8-way distribution panel,  (H3029).

   o   Two interconnecting cables,  (BC05L-xx).

   Figure 1-1 shows major features of the module.   Its dimensions are
   21.4 cm x 39.9 cm (8.41 inches x 15.69 inches).   The module is
   connected to the backplane via connectors A-F.   J1-J4 are
   connected to the communications lines via BC05L cables and
   (H3029) distribution panels.

   DIL switchpacks E173,  E60,  and E121,  select the device address,
   the interrupt vector,  and the interrupt level,  respectively.
    
1 QUICK

   Not supported
      
1 SECTIONS

     There two sections supplied with this diagnostic;
      o  MODEM

      o  ECHO


     The modem section runs a modem loopback test and is  invoked
 by using the vds command ST/SE=MODEM.

     The ECHO section allow a  user  to  select  a  line  with  a
 terminal  attached.  All characters typed on the terminal will be
 checked for errors, then echoed back to the terminal.
 
1 Errors

   The error number appearing in the error printout corresponds
  to the error number found in each test description under errors.

  (i.e.  HELP EHXDH TEST_DESC TEST_26 ERRORS).
   
   All error numbers missing in the above help statement should
  contain enough information in the message itself to let you know whats
  going on.  

   These missing ones should only be system service errors, and
  should not occur if the HARDCORE is working correctly (see 
  HELP EHXDH ENVIRONMENT).

   The number of the line being tested when an error occurrs is
  included in the error printout.

      

1 TEST_DESC
2 Test_1 - Device Address Test
3 Test_Description -

     Verifies that the UUT will  respond  to  the  proper  Q 22 bus
 handshaking  when  accessed.   This test does not test all lines,
 just line 0.



3 Test_Steps -

     1.  verify device responds to its address



3 Errors -

      o  Error 1 - error if  device  failed  to  respond  to  its
         address

2 Test_2 - Master Reset/Selftest Test
3 Test_Description -

         execute selftest and wait for timeout  or  completion

         report  error  if  selftest  not  finished  (timeout)

         error if  selftest  did  not  complete  

    verify  no selftest  error  occurred  

   error  if  selftest  error occurred 

    verify that receive data available is  set

         error if selftest codes are unavailable or missing

         verify that the returned selftest code  is  correct

         error  if selftest code(s) are incorrect 

   read next two codes, they are  rom  version  

   verify  RX available   is  now  clear  

   error  if  data  still available after all selftest codes are read 

   verify rx  data  valid  is  now  clear 

   error if unexpected valid data in rx fifo after codes are read

3 Errors -

      o  1 - caused by master reset not clearing in 5 second

      o  2  -  caused  by  the  diagnostic  fail  bit  being  set
         indicating selftest errors

      o  3 - caused by an unexpected selftest error code

2 Test_3 - Master Reset/Skip Selftest Test
3 Test_Description -

     Verifies that the master reset bit  clears  within  a  short
 time  after  it  is  set  if  the skip selftest sequence is used.
 Verifies that the Skip Selftest return codes are normal.


3 Test_Steps -

     1.  execute skip selftest

     2.  wait for the master reset bit to clear

     3.  verify that the selftest finished

     4.  error if skip selftest failed to complete

     5.  verify that no errors occurred

     6.  error if diagnostic fail bit is set

     7.  test skip selftest codes

     8.  error if rx.avail is clear after skip selftest

     9.  error if skip selftest codes are incorrect

    10.  now read out the two ROM Version codes to clean out  the
         RX FIFO

    11.  verify there are no more valid data in the FIFO

    12.  error if rx.avail still set after all selftest codes are
         read

    13.  error if rx.valid still set after all codes are read


3 Error -

      o  Error 2 - error if skip selftest failed to complete.

      o  Error 3 - error if diagnostic fail bit is set

      o  Error 4 - error if rx.avail is clear after skip selftest

      o  Error 5 - error if skip selftest codes are incorrect

      o  Error 6 - error if rx.avail still set after all selftest
         codes are read

      o  Error 7 - error if rx.valid still set  after  all  codes
         are read


2 Test_4 - Diag Field (BMP) Test
3 Test_Description -

     Verifies that a request for BMP code reporting  is  answered
 by the UUT.


3 Test_Steps -

     1.  request the BMP code

     2.  verify bmp code was returned

     3.  error if DHU did not return BMP code

     4.  verify bmp code is correct

     5.  error if BMP code is unexpected value

     6.  verify that the RX FIFO is empty

     7.  error if rx.avail still set after BMP code is read  from
         rx fifo

     8.  error if rx.valid still set after BMP code is read  from
         rx fifo



3 Errors -

      o  

      o  Error 2 - error if DHU did not return BMP code

      o  Error 3 - error if BMP code is unexpected value

      o  Error 4 - error if rx.avail still set after BMP code  is
         read from rx fifo

      o  Error 5 - error if rx.valid still set after BMP code  is
         read from rx fifo

2 Test_5 - Selftest Forced Failure Test
3 Test_Description -

     Verifies that the selftest will report errors correctly when
 it is forced to fail, and that the diagnostic fail bit will go to
 both the active and inactive states.


3 Test_Steps -

     1.  initialized device

     2.  wait appropriate time, then write force fail code to dhu

     3.  error if selftest failed to complete

     4.  error if selftest did not detect forced error



3 Errors -

      o  Error 2 - error if selftest failed to complete

      o  Error 3 - error if selftest did not detect forced error



2 Test_6 - ROM Version Printout Test
3 Test_Description -

     If requested, reports the version numbers of the 8051 Roms.


3 Test_Steps -

      o  if event flag 1 is clear, continue, else exit

      o  init device

      o  print rom version number in returned codes


3 Errors -

      o  none



2 Test_7 - Register Address Test
3 Test_Description -

     Verifies that  the  registers  can  be  uniquely  addressed.
 Patterns  are written into the registers, and then read back.  If
 all data is not unique (barring undefined  bits)  then  an  error
 condition  exists.  Also verifies that word and and byte accesses
 work properly.  Read or write only registers, or  registers  that
 cause unwanted action are not included.  They are tested later.


3 Test_Steps -

     1.  initialize the device

     2.                 word access test

     3.  loop till lines are done

     4.  set current line number

     5.  loop until all registers have been written

     6.  write data into all indexed registers exept the ones

     7.  not implemented in RAM

     8.  loop until all lines have been verified

     9.  set up line number

    10.  loop until all indexed registers have been checked

    11.  verify patterns except for those indexed  registers  not
         implemented in RAM

    12.  error if word data read not same as word data written

    13.                                 byte access test

    14.  loop until all lines have been written

    15.  select current line

    16.  loop until all indexed registers have been written

    17.  write pattern into indexed register  expcept  those  not
         implemented in RAM

    18.  loop until all line have been verified

    19.  select current line

    20.  loop until all indexed registers have been verified

    21.  verify data in all indexed registers  except  those  not
         implemented in RAM

    22.  error if byte data read not same as byte data written

    23.                         read modify write word test

    24.  choose line zero

    25.  do the operation 10 times

    26.  increment should cause a read  modify  write  operation,
         verify data

    27.  error if read/modify/write word data read  not  same  as
         written

    28.                         read modify write byte test

    29.  choose line zero

    30.  do the operation 10 times

    31.  increment should cause a read  modify  write  operation,
         verify data

    32.  error if read/modify/write word data read  not  same  as
         written


3 Errors -

      o  Error 2 - error if word data read not same as word  data
         written

      o  Error 3 - error if byte data read not same as byte  data
         written

      o  Error 4 - error if read/modify/write word data read  not
         same as written

      o  Error 5 - error if read/modify/write word data read  not
         same as written



2 Test_8 - Id Bit Test
3 Test_Description -

     Verifies that the id bit reads as a one.


3 Test_Steps -

      o  verify ID bit is set



3 Errors -

      o  "error in device initialization, selftest codes = xxxx"

      o  "DHV11 Identification bit not set"



2 Test_9 - TX Enable/TX Action/TX Action FIFO
3 Test_Description -

     Verifies that if a data word is written without the TX  data
 valid  bit  set, no TX actions are generated, and when it is set,
 TX action is generated.


3 Test_Steps -

     1.  loop until all selected units are tested

     2.  intialize device and report selftest codes if  an  error
         occurrs

     3.  verify that TX Action has been reset

     4.  error if tx action not cleared by master reset

     5.  verify that all  TX  Enable  bits  have  inited  to  the
         correct state

     6.  error if tx enable not set by master reset

     7.  verify TX Enable clears on current line only

     8.  error if tx enable clear for line other than current one

     9.  error if current line did not have tx.ena clear

    10.  put all lines into internal loopback mode

    11.  verify TX Action remains clear when character in TX Data
         FIFO and TX Enable is clear

    12.  set line number and stuff a character  in  the  TX  Data
         FIFO

    13.  error if tx action set after data xmission when disabled

    14.  now enable transmitter, wait for character,  and  report
         error if it doesn't

    15.  show up

    16.  error if tx action not set after data transmission  when
         enabled

    17.  verify that, for some really bizarre reason,  dma  error
         did not set

    18.  error if dma error is set

    19.  verify it came in on the correct line

    20.  error if tx action occurred on wrong line

    21.  verify nothing else transmitted that character

    22.  error if more tx actions than expected

    23.  verify that each line can make  an  entry  into  the  TX
         Action FIFO

    24.  fill tx action fifo, stash any tx actions  that  may  be
         left over

    25.  wait for characters

    26.  fetch any more entries that may be there

    27.  verify that no other character came in on the same line

    28.  error if more than one txaction for current line

    29.  verify one entry for each line number

    30.  error if a line failed to return a tx action

    31.  verify that there are no more entries

    32.  error if more txactions than expected



3 Errors -

      o  Error 2 - error if tx action not cleared by master reset

      o  Error 3 - error if tx enable not set by master reset

      o  Error 4 - error if tx enable clear for line  other  than
         current one

      o  Error 5 - error if current  line  did  not  have  tx.ena
         clear

      o  Error 7 - error if tx action  set  after  data  xmission
         when disabled

      o  Error 8  -  error  if  tx  action  not  set  after  data
         transmission when enabled

      o  Error 9 - error if dma error is set

      o  Error 10 - error if tx action occurred on wrong line

      o  Error 11 - error if more tx actions than expected

      o  Error 13 - error if more than one txaction  for  current
         line

      o  Error 14 - error if a line failed to return a tx action

      o  Error 15 - error if more txactions than expected



2 Test_10 - RX Enable/Data Valid/Data Available Test
3 Test_Description -

     Verifies  that  RX  Data  Available  does  not  set  when  a
 character  is  transmitted  to  it  with RX Enable clear, RX Data
 Valid bits remains clear, and that they do set when  a  character
 is received with RX Enable set.


3 Test_Steps -

     1.  error if rx.enable bit set after reset

     2.  set line and maint mode and transmit a character

     3.  verify  that  no  character  received   while   receiver
         disabled

     4.  error if rx.avail  set  when  rx.enable  clear  and  not
         internal loop

     5.  error if rx.valid  set  with  rx.enable  clear  and  not
         internal loop

     6.  internal  loopback,  verify  that  the   character   was
         received

     7.  error if rx.avail remains clear with rx.enable clear and
         internal loop

     8.  error if rx.avail remains clear with rx.enable clear and
         internal loop

     9.  enable receiver

    10.  verify rx enable sets for current line only

    11.  error if rx.enable not set for current line

    12.  error if rx.enable set for other than current line

    13.  set dhu to current line, and transmit a character

    14.  verify that data valid and data available got set

    15.  error if rx.avail clear with rx.enable set

    16.  error if rx.valid clear with rx.enable set

    17.  verify no receiver errors occurred

    18.  error if any error bits set on received data

    19.  verify character came in on correct line

    20.  error if data came in on unexpected line

    21.  verify no other lines recevied a character

    22.  error if rx.avail is still set  after  reading  expected
         data

    23.  error if rx.valid is still set  after  reading  expected
         data



3 Errors -

      o  Error 2 - error if rx.enable bit set after reset

      o  Error 4 - error if rx.avail set when rx.enable clear and
         not internal loop

      o  Error 5 - error if rx.valid set with rx.enable clear and
         not internal loop

      o  Error 6 - error if rx.avail remains clear with rx.enable
         clear and internal loop

      o  Error 7 - error if rx.avail remains clear with rx.enable
         clear and internal loop

      o  Error 8 - error if rx.enable not set for current line

      o  Error 9 - error if rx.enable set for other than  current
         line

      o  Error 11 - error if rx.avail clear with rx.enable set

      o  Error 12 - error if rx.valid clear with rx.enable set

      o  Error 13 - error if any error bits set on received data

      o  Error 14 - error if data came in on unexpected line

      o  Error 15 - error if rx.avail is still set after  reading
         expected data

      o  Error 16 - error if rx.valid is still set after  reading
         expected data



2 Test_11 - Maintenance Mode Test
3 Test_Description -

     This test verifies that the Maintenance  modes  are  working
 correctly.  Works only in staggerred loopback mode.


3 Test_Steps -

     1.  verify all lines  inited  to  correct  maintenance  mode
         (normal mode);

     2.  error if maintenance mode did not initialize to normal

     3.  set line and put it in internal loopback mode

     4.  verify only current line is in internal loop mode

     5.  error if line failed to set to internal maintenance mode

     6.  error if internal mode set on other than current line

     7.  transmit   character   and   allow   enough   time   for
         transmission

     8.  verify that data available is set

     9.  error if rx.avail not set  after  xmission  in  internal
         loop

    10.  verify that data valid is set

    11.  error if rx.valid not set after transmission in internal
         loop

    12.  verify it came in on the correct line number

    13.  error if data received on unexpected line

    14.  verify no errors occurred

    15.  error if data received with errors

    16.  verify the data is correct

    17.  error if data received is not same as transmitted

    18.  set current line in normal mode

    19.  verify current line is normal mode

    20.  error if line failed to set to normal mode

    21.  set adjacent line in loop mode

    22.  transmit   character   and   allow   enough   time   for
         transmission

    23.  error if data not loop back  by  external  connector  in
         normal mode

    24.  error if data received on unexpected line

    25.  error if data received with errors

    26.  error if data received not same as transmitted

    27.  set line to current line again to test auto echo mode

    28.  end of testing



3 Errors -

      o  Error 2 - error if maintenance mode did  not  initialize
         to normal

      o  Error 3 - error  if  line  failed  to  set  to  internal
         maintenance mode

      o  Error 4 - error if  internal  mode  set  on  other  than
         current line

      o  Error 6 - error if rx.avail not set  after  xmission  in
         internal loop

      o  Error 7 - error if rx.valid not set  after  transmission
         in internal loop

      o  Error 8 - error if data received on unexpected line

      o  Error 9 - error if data received with errors

      o  Error 10 -  error  if  data  received  is  not  same  as
         transmitted

      o  Error 11 - error if line failed to set to normal mode

      o  Error 13 - error if  data  not  loop  back  by  external
         connector in normal mode

      o  Error 14 - error if data received on unexpected line

      o  Error 15 - error if data received with errors

      o  Error  16  -  error  if  data  received  not   same   as
         transmitted

2 Test_12 - RX FIFO Test
3 Test_Description -

     This test verifies that the fifo locations can  be  uniquely
 addressed  from  the  Q 22 bus.  The FIFO is filled with 256 unique
 bytes of data, and then checked for data integrity.


3 Test_Steps -

     1.  initialize device

     2.  set current line number, enable receiver, fill rx  silo.
         Report any tx failures

     3.  verify that the character has been xmitted

     4.  error if data failed to get transmitted

     5.  verify that csr data available bit is set

     6.  error rx.avail clears before rx fifo is empty

     7.  verify that no errors have occurred

     8.  error if data received with errors

     9.  error if data received is not same as transmitted

    10.  verify that the line number is okay

    11.  error if data received on unexpected line



3 Errors -

      o  Error 3 - error if data failed to get transmitted

      o  Error 4 - error rx.avail clears before rx fifo is empty

      o  Error 5 - error if data received with errors

      o  Error 6  -  error  if  data  received  is  not  same  as
         transmitted

      o  Error 7 - error if data received on unexpected line



2 Test_13 - Interrupts Test
3 Test_Description -

     Verifies that the TX.  and RX.  interrupts work correctly


3 Test_Steps -

     1.  initialize device

     2.  enable adapter interrupts and report any errors doing so

     3.  set interrupt enable bits and verify they are set

     4.  verify the bits aren't stuck

     5.  error if interrupt enable bits failed to set

     6.  set master reset and wait for it to get done

     7.  error if reset failed to complete

     8.  error if interrupt enable bits were  cleared  by  master
         reset

     9.  init Q 22 bus and report any errors

    10.  verify that the interrupt enable bits  were  cleared  by
         Q 22 bus init.

    11.  error if bits not cleared by Q 22 bus init

    12.  clear out the interrupt enable bits

    13.  set loopback mode for this line

    14.  transmit a character and report  any  errors  doing  so,
         then clean out the silos

    15.  clean out the silos

    16.  verify that no  interrupts  occurred  with  the  DHU/DHV
         interrupts disabled

    17.  error if interrupts occurred with interrupts disabled

    18.  enable tx interrupts only, xmit a character,  and  clean
         out silos

    19.  clean out the silos

    20.  verify  that  tx  interrupt  occurred  and  only  a   tx
         interrupt occurred

    21.  error if unexpected interrupt occurred

    22.  error if rx interrupt occurred, or tx  interrupt  failed
         to occur

    23.  verify the vector is okay

    24.  error if tx interrupt occurred at wrong vector

    25.  verify that the br level is correct.  16  is  subtracted
         since

    26.  the IPL is different by that much.

    27.  error if interrupt was requested at wrong level

    28.  clear interrupt flags, disable xmit  interrupts,  enable
         rx interrupts

    29.  xmit a character and report any errors, then  clean  out
         silo

    30.  clean out the silos

    31.  verify that a rx  interrupt  and  only  a  rx  interrupt
         occurred

    32.  error if unexpected error occurred

    33.  error if tx interrupt occurred or rx interrupt failed to
         occur

    34.  verify rx interrupted at correct vector

    35.  error if interrupt occurred at wrong vector

    36.  verify rx interrupted at correct br level

    37.  error if interrupt requested at wrong br level

3 Errors -

   o Error 5 - error if interrupt enable bits failed to set

   o Error 6 - error if reset failed to complete

   o Error 7 - error if interrupt enable bits were cleared by master reset

   o Error 9 - error if bits not cleared by Q BUS init

   o Error 12 - error if interrupts occurred with interrupts disabled

   o Error 14 - error if unexpected interrupt occurred

   o Error 15 - error if rx interrupt occurred, or tx interrupt failed to o
ccur

   o Error 17 - error if unexpected error occurred

   o Error 18 - error if tx interrupt occurred or rx interrupt failed to oc
cur




2 Test_14 - DMA Start/DMA Abort Test
3 Test_Description -

     Verifies that each DMA start bit will initiate a DMA TX on a
 line, that it can be aborted and resumed, and that DMA aborts and
 completions cause interrupts.


3 Test_Steps -

     1.  initialize device

     2.  enable interrupts Q 22 bus adapter interrupts, and dhu/dhv
         interrupts

     3.  init all diagnostic flags

     4.  set line number

     5.  set internal loop

     6.  set tx address, and count

     7.  allow time for loopback to engage

     8.  fire up the DMA and allow 1 second before timing out

     9.  see if unexpected interrupt

    10.  Error if unexpected Error occurred during DMA

    11.  check to see if the DMA completed

    12.  Error if the DMA timed out or failed to cause  interrupt
         when done

    13.  verify tx action is set

    14.  Error if DMA did not cause tx.action to set

    15.  verify no DMA errors occurred

    16.  Error if DMA Error occurred

    17.  verify that the DMA start bit has been cleared

    18.  Error if dma start bit is still set after completion

    19.  verify that no other tx action occurred

    20.  Error if unexpected tx.action in action fifo

    21.  TEST DMA ABORTS

    22.  enable adapter interrupts

    23.  enable device interrupts

    24.  create a mask to compare with txaction flags  for  lines
         that have completed

    25.  loop to set up all lines

    26.  set line number

    27.  set internal loop

    28.  setup dma

    29.  allow time for loopback to engage

    30.  set a one second timer

    31.  fire up the dma's

    32.  loop here until we are sure all dma's have been aborted

    33.  Error if all dma's not aborted within two seconds

    34.  verify everything turned out okay

    35.  verify that we have received an interrupt from  the  DMA
         abort

    36.  Error if DMA abort did not cause interrupt

    37.  verify that the DMA has truly stopped

    38.  Error if DMA abort did not stop the DMA

    39.  verify the start bit is cleared

    40.  Error if DMA abort did not clear DMA start bit

    41.  verify no dma Error occurred

    42.  Error if DMA Error is set after a DMA abort

    43.  verify no other tx action occurred

    44.  verify that the address and byte count are okay

    45.  clear abort bit and set start bit to restart the dma

    46.  set line number

    47.  clear abort, set start in buffered regs

    48.  write buffered regs to device

    49.  loop here until we are sure all dma's have been aborted

    50.  Error if all dma's not aborted within two seconds

    51.  verify that we have received an interrupt

    52.  Error if DMA did not interrupt after restart

    53.  verify the start bit is cleared

    54.  Error if DMA start bit not clear on  completion  of  DMA
         after restart

    55.  verify no dma Error occurred

    56.  Error if DMA Error bit is set after restarting the DMA

    57.  verify no other tx action occurred

    58.  Error if mor than one tx.action  in  action  fifo  after
         restart


3 Errors -

   o Error 4 - error if unexpected error occurred during DMA

   o Error 5 - error if the DMA timed out or failed to cause interrupt when
 done

   o Error 6 - error if DMA did not cause tx.action to set

   o Error 7 - error if DMA error occurred

   o Error 8 - error if dma start bit is still set after completion

   o Error 9 - error if unexpected tx.action in action fifo

   o Error 14 - error if all dma's not aborted within two seconds

   o Error 15 - error if DMA abort did not cause interrupt

   o Error 16 - error if DMA abort did not stop the DMA

   o Error 17 - error if DMA abort did not clear DMA start bit

   o Error 18 - error if DMA error is set after a DMA abort

   o Error 19 - error if unexpected tx.action in the action fifo

   o Error 21 - error if all dma's not aborted within two seconds

   o Error 22 - error if DMA did not interrupt after restart

   o Error 23 - error if DMA start bit not clear on completion of DMA after
 restart

   o Error 24 - error if DMA error bit is set after restarting the DMA

   o Error 25 - error if mor than one tx.action in action fifo after restar
t


2 Test_15 - Byte Count Register Test
3 Test_Description -

     This test  verifies  that  the  byte  count  registers  work
 properly.   Data  is  not  checked  since we are not certain that
 addressing works okay,  but  the  number  of  bytes  received  is
 tallied  for  each  line  and checked to see if it is the same as
 transmitted.


3 Test_Steps -

     1.  initialize device

     2.  enable interrupts Q 22 bus adapter interrupts, and dhu/dhv
         interrupts

     3.  set line to zero and enable interrupts

     4.  initialize received character counter,  speed,  internal
         loop, and set up dma

     5.  set internal loopback

     6.  set speed

     7.  set the address and fire up the DMA

     8.  set up a 2 minute timer in case DMA hangs

     9.  error if timeout occurred before DMA interrupted

    10.  cancel the timer

    11.  error if number of bytes received is incorrect



3 Errors -

   o Error 5 - error if timeout occurred before DMA interrupted

   o Error 7 - error if number of bytes received is incorrect



2 Test_16 - DMA Address/Byte Count Test
3 Test_Description -

     Tests the ability of the device to increment  addresses  and
 byte  counts correctly.  A DMA of 2048k bytes of decremeting data
 will be fired up and verified for data integrity and  no  errors.
 This  test  is  performed on one line only since the DMA logic is
 common to  all  lines,  and  the  memory  containing  the  lines'
 addresses  and  byte counts has been checked by the selftest.  It
 will be repeated until all address lines have been touched.


3 Test_Steps -

     1.  initialize device

     2.  enable interrupts Q 22 bus adapter interrupts, and dhu/dhv
         interrupts

     3.  set line

     4.  set DMA address and byte count

     5.  set internal loop

     6.  set line

     7.  set DMA address and byte count

     8.  set internal loopback

     9.  now fire up the DMAs

    10.  if any have completed, save the TX action or we'll  lose
         it due to

    11.  a csr read when we change the line number

    12.  set a one minute timer in case DMA hangs

    13.  error if timeout occurred before DMAs interrupted

    14.  now verify that the data has come through okay

    15.  verify that no errors occurred

    16.  verify the valid bit is set

    17.  error if no data was received

    18.  verify no errrors occurred

    19.  error if data errors occurred in received data

    20.  verify the data is correct

    21.  error if data received not same as transmitted



3 Errors -

   o Error 5 - error if timeout occurred before DMAs interrupted

   o Error 7 - error if no data was received

   o Error 8 - error if data errors occurred in received data

   o Error 9 - error if data received not same as transmitted


2 Test_17 - Speed Test
3 Test_Description -

     This test will transmit characters  at  all  speeds  on  all
 lines in internal loopback mode.  This test uses the xmit FIFO to
 send characters.


3 Test_Steps -

     1.  create a mask to compare with txaction flags  for  lines
         that have completed

     2.  initialize device

     3.  enable adapter interrupts

     4.  enable device interrupts

     5.  verify all lines inited to correct speed

     6.  error if line speed not initialized to 9600 bps

     7.  loop until all speeds are tested

     8.  set current speed

     9.  clear out the abort bit

    10.  set up dma

    11.  wait for loopbacks to take hold

    12.  fire up the dmas

    13.  set timer for one second and  transmit  until  timer  is
         done

    14.  wait for all dmas be aborted

    15.  error if all dma's not aborted within two seconds

    16.  now check number of characters xmitted

    17.  verify  that  number  of  characters  is  greater   than
         previous xmission

    18.  error if not enough characters transmitted  for  current
         speed

    19.  stash the current number of characters xmitted

    20.  speed too fast for normal check,  just  verify  TX  fifo
         filled up a couple of times

    21.  error if not enough characters transmitted  for  current
         speed

3 Errors -

   o Error 4 - error if line speed not initialized to 9600 bps

   o Error 6 - error if all dma's not aborted within two seconds

   o Error 7 - error if not enough characters transmitted for 
            current speed

   o Error 8 - error if not enough characters transmitted for 
            current speed

2 Test_18 - XON/XOFF Recognition Test
3 Test_Description -

     Verifies that XON/XOFF control is working properly


3 Test_Steps -

     1.  initialize flags

     2.  now init the device

     3.  enable adapter interrupts

     4.  set i.auto, o.auto, force xoff

     5.  verify i.auto was set

     6.  error if i.auto failed to set

     7.  verify o.auto was set

     8.  error if 0.auto failed to set

     9.  verify force xoff was set

    10.  error if force xoff failed to set

    11.  now init the device

    12.  verify  force  xoff,  i.auto,  and  o.auto  are   inited
         correctly

    13.  verify i.auto was clear

    14.  error if i.auto not cleared by initialize

    15.  verify o.auto was clear

    16.  error if o.auto not cleared by initialize

    17.  verify force xoff was clear

    18.  error if force xoff not cleared by initialize

    19.  enable device interrupts

    20.  verify force xoff sets for this line only

    21.  set line number

    22.  set internal loop if internal loop was selected

    23.  looptype is not internal, set  normal  mode  and  enable
         receiver

    24.  if staggered loop, set up adjacent line

    25.  set adjacent line number

    26.  set normal mode, and receive enable

    27.  write lcr to device and line number and restore buffered
         registers

    28.  set the force xoff bit for this line

    29.  see if current line

    30.  current line, verify bit is set

    31.  error if force xoff failed to set for this line

    32.  verify force xoff causes board  to  generate  xoffs  and
         xons

    33.  see if we have a character in the fifo

    34.  error if no data received when force xoff set

    35.  see if it is an XOFF character

    36.  error if data is not force xoff character

    37.  see if it came in on the right line

    38.  error if xoff received on unexpected line

    39.  error if xoff received on unexpected line

    40.  verify no other characters have been received

    41.  error if unexpected data in rx fifo

    42.  not the same line, verify it is clear

    43.  error if force xoff set on unexpected line

    44.  set current line again and clear force xoff

    45.  verify that it is clear

    46.  error if force xoff didn't clear for current line

    47.  wait for xon to be xmitted

    48.  get next character in RX FIFO

    49.  see if we have a character in the fifo

    50.  error if data not received when force xoff is cleared

    51.  see if it is an XON character

    52.  error if received data was not a xon character

    53.  see if it came in on the right line

    54.  staggerred loop, see if received on adjacent line

    55.  error  if  xon  not  received  on  adjacent  line   with
         staggered loop

    56.  loopback on same line

    57.  error if xon not received on current line

    58.  verify no more characters have been received

    59.  error if rx.avail still set  after  xoff/xon  characters
         read

    60.  test automatic output control function

    61.  verify that force xoff has  no  effect  when  o.auto  is
         clear

    62.  set up this line for dma

    63.  fire up the dma, wait for a few characters to xmit, then
         force xoff

    64.  now wait for xmission to complete

    65.  if timeout, then xoff probably stopped the dma and  this
         is bad

    66.  error if timeout occurred during DMA when xoff sent  and
         o.auto clear

    67.  cancel timer

    68.  clear xoff

    69.  wait for xon to be  xmitted,  and  time  for  it  to  be
         received

    70.  flush the RX and TXACTION FIFOs

    71.  clear diagnostic flags

    72.  now set automatic output control (o.auto)

    73.  set up dma again

    74.  now fire up the dma, wait a bit

    75.  force xoff, on adjacent line if staggered

    76.  not staggered, force xoff on current line

    77.  staggered, set line to adjacent line

    78.  set xoff

    79.  now allow enough time for the xmission to complete

    80.  if NO timeout, then xoff failed to suspend  transmission
         and this is bad

    81.  error if DMA completed after sending  xoff  with  o.auto
         enabled

    82.  cancel timer and clear timeout flag

    83.  clear xoff, this forces xon to be xmitted

    84.  now restore original line number

    85.  wait for dma to complete

    86.  if timeout, then xon failed to restart transmission  and
         this is bad

    87.  error if DMA timed out after sending xon after xoff with
         o.auto enabled

    88.  cancel timer, and flush the fifo

    89.  verify that o.auto can be cleared

    90.  error if o.auto failed to clear



3 Errors -

   o Error 4 - error if i.auto failed to set

   o Error 5 - error if 0.auto failed to set

   o Error 6 - error if force xoff failed to set

   o Error 8 - error if i.auto not cleared by initialize

   o Error 9 - error if o.auto not cleared by initialize

   o Error 10 - error if force xoff not cleared by initialize

   o Error 13 - error if force xoff failed to set for this line -

   o Error 16 - error if no data received when force xoff set

   o Error 17 - error if data is not force xoff character

   o Error 18 - error if xoff received on unexpected line

   o Error 19 - error if xoff received on unexpected line

   o Error 20 - error if unexpected data in rx fifo

   o Error 21 - error if force xoff set on unexpected line

   o Error 22 - error if force xoff didn't clear for current line

   o Error 25 - error if data not received when force xoff 
            is cleared

   o Error 26 - error if received data was not a xon character

   o Error 27 - error if xon not received on adjacent line 
            with staggered loop

   o Error 28 - error if xon not received on current line

   o Error 29 - error if rx.avail still set after xoff/xon 
            characters read

   o Error 31 - error if timeout occurred during DMA when xoff 
            sent and o.auto clear

   o Error 35 - error if DMA completed after sending xoff with 
            o.auto enabled

   o Error 37 - error if DMA timed out after sending xon after 
            xoff with o.auto enabled

   o Error 38 - error if o.auto failed to clear




2 Test_19 - Data Format Test
3 Test_Description -

         This test will check out that all sizes and formats work
 properly.  10 characters will be used in this test, and each line
 will be checked out.


3 Test_Steps -

     1.  initialize flags and device

     2.  enable device interrupts

     3.  set line number, loopback type and speed

     4.  set current line parameters

     5.  set up for 10 byte dma

     6.  fire up the DMAs

     7.  see if TXACTION was set, stach it if it was

     8.  set dma start bit

     9.  set a timer

    10.  wait for all the DMAs to complete

    11.  wait one more second for all the data to go through

    12.  verify that no timeout occurred

    13.  error if DMAs timed out

    14.  cancel the timer

    15.  verify no errors occurred

    16.  verify that the dma error bit is clear

    17.  error if a DMA error occurred

    18.  verify that no data or receive errors occurred

    19.  verify no receiver errors occurred

    20.  error if data received with errors

    21.  verify data is okay

    22.  error if data received is not same as transmitted



3 Errors -

   o Error 5 - Error if DMAs timed out

   o Error 6 - Error if a DMA error occurred

   o Error 7 - Error if data received with   errors

   o Error 8 - Error if data received is not same as transmitted

2 Test_20 - Modem Signal Test
3 Test_Description -

     Verifies that changing the UUT line control DTR bit  affects
 the  state  of  the dtr control line, looped signals, and that no
 unexpected bits are set, and verifies that changing the UUT  line
 control rts bit affects the state of the rts control line.


3 Test_Steps -

     1.  initialize the diagnostic flags and the device

     2.  enable interrupts

     3.  set device interrupt enable bits

     4.  set dtr, rts, and link bits

     5.  verify all the bits set

     6.  error if DTR, RTS or LINK bits of the lcr failed to set

     7.  now reset the device

     8.  error if reset to clear modem control bits timed out

     9.  clear out all selftest codes

    10.  set line number and fetch LCR and LSR

    11.  verify that all modem control and status were cleared by
         master reset

    12.  error if reset failed to clear modem control and  status
         bits

    13.  set line number

    14.  see if link should be set on current line,  or  adjacent
         line

    15.  now set link bit

    16.  now restore line

    17.  set DTR link bit

    18.  allow time for device to read modem signals

    19.  check that dtr and rts is clear on all other  lines  but
         current one

    20.  set line number and fetch LCR

    21.  see if this is the current line

    22.  yes it is, verify that DTR is set

    23.  error if DTR failed to set for current line

    24.  verify that RTS is not stuck to DTR

    25.  error if rts is set for current line

    26.  not current line, verify that DTR is clear

    27.  error if DTR set for line other than current line

    28.  see if we are in staggerred loopback

    29.  staggerred loop, see if this line has bits set

    30.  not the adjacent line, verify RING and DSR are clear

    31.  error if DSR and RING are set on unexpected line

    32.  verify link bit is not set on unexpected line

    33.  yes, adjacent line, verify that DSR and RING are set

    34.  error if DSR and RING not set on expected line

    35.  verify that CTS and DCD are not stuck to them

    36.  error if CTS and DCD are unexpectedly set

    37.  verify link bit is not unexpectedly clear

    38.  error if link bit not set on adjacent line

    39.  check for correct interrupt on modem status change

    40.  error if status change did not occur, or did  not  occur
         correctly

    41.  H325 single line loopback, see if this  is  the  current
         line

    42.  current line, verify that RING and DSR are set ;  H325

    43.  error if ring and dsr are not set  for  current  line  ;
         H325

    44.  verify that CTS and DCD are not stuck to them ;  H325

    45.  error if cts and dcd are unexpectedly set with  dtr  set
         and rts clear ;  H325

    46.  not current line, verify DSR and RING are clear ;  H325

    47.  error if dsr and ring set on unexpected line ;  H325

    48.  restore line and clear DTR

    49.  verify that it is clear

    50.  error if dsr failed to clear

    51.  wait for status to change

    52.  see if this is staggered mode

    53.  fetch LSR and verify that RI and DSR are clear

    54.  error if ring and dsr failed to clear

    55.  verify interrupt for modem status change

    56.  set RTS

    57.  verify that RTS got set on this line only

    58.  set line number and fetch LCR

    59.  if current line, make sure RTS is set

    60.  error if rts failed to set for current line

    61.  not current line, so make sure it is clear

    62.  error if rts set on unexpected line

    63.  verify RING and DCD are the only bits  set  and  on  the
         correct line

    64.  check for staggered loop

    65.  staggered loop, see if this is the adjacent line

    66.  error if cts or dcd clear on current line  in  staggered
         loop

    67.  verify the other bits are not set

    68.  error if dsr or ring are set with dtr clear and rts  set
         in staggered loop

    69.  check for correct interrupt on modem status change

    70.  error if status change did not occur, or did  not  occur
         correctly

    71.  not correct line, see if the bits are clear

    72.  error if cts and dcd set on unexpected line in staggered
         loop

    73.  single line loopback, see if this is the correct line

    74.  current line, verify CTS and DCD are set

    75.  error if cts and dcd clear on  current  line  with  h325
         loop

    76.  verify no other bits are set

    77.  error if dsr or ring set with dtr clear and rts  set  in
         h325 loop

    78.  check for correct interrupt on modem status change

    79.  error if status change did not occur, or did  not  occur
         correctly

    80.  error if cts or dcd set on unexpected line in h325 loop

    81.  now restore line

    82.  clear RTS

    83.  verify that it is clear

    84.  error if rts failed to clear

    85.  see if this is staggered loop

    86.  set adjacent line number for staggered loop

    87.  fetch LSR and verify that CTS and DCD are clear

    88.  error if cts and dcd failed to clear when rts cleared

    89.  verify interrupt for modem status change

    90.  error no clearing  RTS  failed  to  cause  modem  status
         change

    91.  clear link bit



3 Errors -

   o Error 4 - error if DTR, RTS or LINK bits of the lcr failed to set

   o Error 5 - error if reset to clear modem control bits timed out

   o Error 6 - error if reset failed to clear modem control and 
            status bits

   o Error 7 - error if DTR failed to set for current line

   o Error 8 - error if rts is set for current line

   o Error 9 - error if DTR set for line other than current line

   o Error 10 - error if DSR and RING are set on unexpected line

   o Error 12 - error if DSR and RING not set on expected line

   o Error 13 - error if CTS and DCD are unexpectedly set

   o Error 14 - error if link bit not set on adjacent line

   o Error 15 - error if status change did not occur, or did not 
            occur correctly

   o Error 16 - error if ring and dsr are not set for current 
            line ; H325

   o Error 17 - error if cts and dcd are unexpectedly set with 
            dtr set and rts clear ; H325

   o Error 19 - error if dsr and ring set on unexpected line 
            ; H325

   o Error 20 - error if dsr failed to clear

   o Error 21 - error if ring and dsr failed to clear

   o Error 23 - error if rts failed to set for current line

   o Error 24 - error if rts set on unexpected line

   o Error 25 - error if cts or dcd clear on current line   
            in staggered loop

   o Error 26 - error if dsr or ring are set with dtr clear 
            and rts set in staggered loop

   o Error 27 - error if status change did not occur, or did 
            not occur correctly

   o Error 28 - error if cts and dcd set on unexpected line 
            in staggered loop

   o Error 29 - error if cts and dcd clear on current line with 
            h325 loop

   o Error 30 - error if dsr or ring set with dtr clear and rts 
            set in h325 loop

   o Error 31 - error if status change did not occur, or did not 
            occur correctly

   o Error 32 - error if cts or dcd set on unexpected line in 
            h325 loop

   o Error 33 - error if rts failed to clear

   o Error 34 - error if cts and dcd failed to clear when rts cleared

   o Error 35 - error no clearing RTS failed to cause modem 
            status change


2 Test_21 - Framing Error/Break Bit Test
3 Test_Description -

     Verifies that forced framing errors are reported correctly.


3 Test_Steps -

     1.  set up the line

     2.  set up the adjacent line to different data size

     3.  set current line and transmit the character

     4.  verify that the adjacent line got a framing error

     5.  error if no frame  error  when  transmit  data  size  is
         different from receive

     6.  print framing error test skipped

     7.  set break bit and loop mode

     8.  now wait a second, then verify that framing error is set
         for all lines

     9.  set break bit

    10.  see if this is staggered loop mode

    11.  yes, set line to adjacent line

    12.  error if setting break bit did not cause framing error



3 Errors -

    o Error 2 - error if no frame error when transmit data size 
         is different from receive

    o Error 3 - error if setting break bit did not cause 
         framing error


2 Test_22 - Parity Generation/Detection Test
3 Test_Description -

   Verifies that all selected lines can detect
 Parity errors.  Runs only if staggered loopback is
 selected.



3 Test_Steps -

     1.  see if staggered loop

     2.  initialize the device

     3.  set line

     4.  enable receiver and parity to odd

     5.  set adjacent line to opposite parity

     6.  enable receiver

     7.  enable parity and set it to opposite parity

     8.  transmit a character and wait for it

     9.  see if current line got a parity error

    10.  error  if  no  parity  error  when  transmit  parity  is
         different from receive parity



3 Errors -

      o  Error 2 - error if no parity error when transmit  parity
         is different from receive parity



2 Test_23 - Overrun Detection Test
3 Test_Description -

         Verifies that the UUT will receive the maximum number of
 characters  without  causing and overrun error, and that one more
 character will cause overrun.


3 Test_Steps -

     1.  set internal loopback mode

     2.  overfill rxfifo

     3.  wait for xmit then clear out the tx action

     4.  read 255 characters

     5.  verify no overrun error occurred

     6.  error if overrun error occurred unexpectedly

     7.  verify the next character has overrun error and is null

     8.  error if overrun error bit is not set

     9.  verify the character is a null character

    10.  error if data with overrun is not null character



3 Errors -

      o  Error 2 - error if overrun error occurred unexpectedly

      o  Error 3 - error if overrun error bit is not set

      o  Error 4 -  error  if  data  with  overrun  is  not  null
         character



2 Test_24 - Exerciser Test

3 Test_Description -
         This test will get all lines transmitting  at  the  same
 time.   The  speed used will be 4800 bps as that is what the spec
 says the        DHU can run at with all lines full  duplex.   All
 lines will be set       up,  then  the  DMAs will be fired off as
 quickly as possible.  1024      byte buffers  will  be  used  for
 transmission and reception.  The        format  will be 8 bit, no
 parity, and 1 stop bit.


3 Test_Steps -

     1.  initialize device

     2.  enable adapter interrupts

     3.  enable device interrupts

     4.  set up necessary stuff

     5.  set address

     6.  set line speed, enaable parity, set maintenance mode

     7.  set internal loopback if selected

     8.  if staggered loopback, enable adjacent line

     9.  enable receiver

    10.  restore line number

    11.  now write all that into the device registers

    12.  delay for loopbacks to take affect

    13.  enable a timer

    14.  fire up all the DMAs

    15.  save tx action if one has completed

    16.  set line number and start it up

    17.  wait for all the DMAs to complete

    18.  wait one more second for all the data to go through

    19.  verify that no timeout occurred

    20.  error if timceout occurred before DMAs completed

    21.  cancel the timer

    22.  verify that no errors occurred

    23.  verify that the dma error bit is clear

    24.  error if DMA errors occurred

    25.  verify that all data was received

    26.  error if not all data received

    27.  verify that no data or receive errors occurred

    28.  verify no receiver errors occurred

    29.  error if data received with errors

    30.  verify data is okay

    31.  error if data received is not same as data transmitted




3 Errors -

    o Error 4 - error if timceout occurred before DMAs completed

    o Error 6 - error if DMA errors occurred

    o Error 7 - error if not all data received

    o Error 8 - error if data received with errors

    o Error 9 - error if data received is not same as data transmitted




2 Test_25 - Modem Loop Test

3 Test_Description -

        This test runs on a modem that is in loopback mode, or  a
 remote modem in remote loopback mode.
 3 Test Steps -

     1.  enable adapter and device interrupts

     2.  set line number and speed

     3.  enable the receiver

     4.  set up and fire up dma

     5.  set a two minute timer

     6.  wait for the device to complete

     7.  verify that a timeout did not occurr

     8.  error if timeout occurred before DMA completed

     9.  verify data

    10.  verify no receive errors occurred

    11.  error if data was received with errors

    12.  verify no data errors occurred

    13.  error if data received was not same as transmitted




3 Errors -

    o Error 4 - error if timceout occurred before DMAs completed

    o Error 6 - error if DMA errors occurred

    o Error 7 - error if not all data received

    o Error 8 - error if data received with errors

    o Error 9 - error if data received is not same as data transmitted




2 Test_26 - Terminal Echo Test
3 Test_Description -

        This test loops back all characters received on  a  line.
 The     operator  is  queried  as to which line the data is to be
 echoed to.      This will allow isolation of the direction a line
 may be failing.  Type control C to exit test.



3 Test_Steps -

     1.  initialize device

     2.  enable adapter and device interrupts

     3.  set line number and speed

     4.  enable the receiver for this line

     5.  see if a character has been typed

     6.  transmit all characters that we have received

     7.  verify received character has no errors

     8.  error if data received with errors

     9.  set a timer

    10.  transmit and wait for the character

    11.  verify no timeout occurred

    12.  error if timeout before character was transmitted

    13.  cancel timer and reset interrupt flag




3 Errors -

      o  Error if data received with errors


2 Test_27 - I.AUTO Test

3 Test_Description -

     Verifies the i.auto bit works correctly



3 Assumptions -

     All previous tests have successfully run



3 Test_Steps -

     1.  initialize flags

     2.  now init the device

     3.  enable adapter interrupts

     4.  enable device interrupts

     5.  START OF AUTOMATIC INPUT CONTROL TESTING

     6.  set device to current line

     7.  enable receivers

     8.  staggered loop, set line to adjacent one

     9.  enable receiver

    10.  fill the RX fifo with data

    11.  wait for character to go

    12.  error if xmit timed out

    13.  verify no xoff or xons transmitted when i.auto clear

    14.  error if xoff in rx fifo when filled past 3/4 and i.auto
         clear

    15.  verify i.auto sets for this line only

    16.  see if this is the current line under test

    17.  same line, verify it is set

    18.  error if i.auto failed to set on current line

    19.  not the current line under test, verify its clear

    20.  error if i.auto set on other than current line

    21.  reset line number

    22.  if staggered mode, set line to adjacent line

    23.  fill rx fifo past 3/4 full to make it xmit xoff

    24.  wait for character to go

    25.  error if xmit timed out

    26.  read data until an xoff is encountered

    27.  error if xoff not xmitted with i.auto enabled

    28.  error if xoff occured way beyond it's appointed time

    29.  error if xon not xmitted with i.auto enabled

    30.  error if xon occured way beyond it's appointed time

    31.  now shut off automatic output control

    32.  reset original line number

    33.  make sure i.auto for current line is clear

    34.  flush fifo

3 ERRORS: -

   o Error 4 - error if xmit timed out

   o Error 5 - error if xoff in rx fifo when filled past 
            3/4 and i.auto clear

   o Error 6 - error if i.auto failed to set on current line

   o Error 7 - error if i.auto set on other than current line

   o Error 8 - error if xmit timed out

   o Error 9 - error if xoff not xmitted with i.auto enabled

   o Error 10 - error if xoff occured way beyond it's appointed time

   o Error 11 - error if xon not xmitted with i.auto enabled

   o Error 12 - error if xon occured way beyond it's appointed time





2 Test_28 - Split Speed Test Part A

3 Test_Description - -

     This  test  verifies  that  split  speed   operations   work
  correctly This test works in staggered loopback only.



3 Assumptions -

      o  all hardware up to (but not  including)  the  device  is
         working

      o  previous tests have successfully run, otherwise  results
         may be meaningless




3 Test_Steps -

     1.  create a mask to compare with txaction flags  for  lines
         that have completed

     2.  enable adapter interrupts

     3.  enable device interrupts

     4.  loop for line speeds

     5.  loop for adjacent line speeds

     6.  clear line setup mask

     7.  loop to set up all lines

     8.  set line number and speed

     9.  enable receiver

    10.  set dma address and byte count

    11.  flag this line as set up

    12.  set up adjacent line

    13.  set speed

    14.  enable receiver

    15.  set dma address and byte count

    16.  flag this line as having been set up

    17.  set a one second timer

    18.  fire up the dma's

    19.  fire up the adjacent line

    20.  flag it as started

    21.  loop here until we are sure all dma's have been aborted

    22.  see if this line has been checked yet

    23.  flag line as having been checked

    24.  verify this lines speeds are okay

    25.  error if transmit speed did not set to correct speed

    26.  error if receive speed did not set to correct speed

    27.  verify data for line

    28.  error if data received with errors or invalid

    29.  error if data received on  adjacent  line  not  same  as
         transmitted

    30.  flag adjacent line as already tested

    31.  verify this lines speeds are okay

    32.  error if transmit or receive speeds are not  at  correct
         speed

    33.  verify the TX count is okay

    34.  error if less data than expected was transmitted

    35.  now verify adjacent line

    36.  set line to adjacent line

    37.  error if data received with errors on the other line

    38.  error if data received not same as transmitted

    39.  verify the TX count is okay

    40.  error if less data than expected was transmitted

    41.  reset setup flags and adjacent speed table

3 Errors -

   o Error 5 - error if transmit speed did not set to correct speed

   o Error 6 - error if receive speed did not set to correct speed

   o Error 7 - error if data received with errors or invalid

   o Error 8 - error if data received on adjacent line not same 
            as transmitted

   o Error 9 - error if transmit or receive speeds are not at 
            correct speed

   o Error 10 - error if less data than expected was transmitted

   o Error 11 - error if data received with errors on the other line

   o Error 12 - error if data received not same as transmitted

   o Error 13 - error if less data than expected was transmitted





2 Test_29 - Split Speed Test Part B

3 Test_Description -

     This  test  verifies  that  split  speed   operations   work
  correctly This test works in staggered loopback only.



3 Assumptions -

      o  all hardware up to (but not  including)  the  device  is
         working

      o  previous tests have successfully run, otherwise  results
         may be meaningless

3 Test_Steps -

     1.  create a mask to compare with txaction flags  for  lines
         that have completed

     2.  enable adapter interrupts

     3.  enable device interrupts

     4.  loop for line speeds

     5.  loop for adjacent line speeds

     6.  clear line setup mask

     7.  loop to set up all lines

     8.  set line number and speed

     9.  enable receiver

    10.  set dma address and byte count

    11.  flag this line as set up

    12.  set up adjacent line

    13.  set speed

    14.  enable receiver

    15.  set dma address and byte count

    16.  flag this line as having been set up

    17.  set a one second timer

    18.  fire up the dma's

    19.  fire up the adjacent line

    20.  flag it as started

    21.  loop here until we are sure all dma's have been aborted

    22.  see if this line has been checked yet

    23.  flag line as having been checked

    24.  verify this lines speeds are okay

    25.  error if transmit speed did not set to correct speed

    26.  error if receive speed did not set to correct speed

    27.  verify data for line

    28.  error if data received with errors or invalid

    29.  error if data received on  adjacent  line  not  same  as
         transmitted

    30.  flag adjacent line as already tested

    31.  verify this lines speeds are okay

    32.  error if transmit or receive speeds are not  at  correct
         speed

    33.  verify the TX count is okay

    34.  error if less data than expected was transmitted

    35.  now verify adjacent line

    36.  set line to adjacent line

    37.  error if data received with errors on the other line

    38.  error if data received not same as transmitted

    39.  verify the TX count is okay

    40.  error if less data than expected was transmitted

    41.  reset setup flags and adjacent speed table

3 Errors -

   o Error 5 - error if transmit speed did not set to correct speed

   o Error 6 - error if receive speed did not set to correct speed

   o Error 7 - error if data received with errors or invalid

   o Error 8 - error if data received on adjacent line not same 
            as transmitted

   o Error 9 - error if transmit or receive speeds are not at 
            correct speed

   o Error 10 - error if less data than expected was transmitted

   o Error 11 - error if data received with errors on the other line

   o Error 12 - error if data received not same as transmitted

   o Error 13 - error if less data than expected was transmitted


DUA1:<SYS0.SYSMAINT>EHXVS.HLP;1
===============================
1 Help
  EHXVS

  EHXVS is a standalone diagnostic which currently supports the VCB01
  module for the VS200 Graphics Workstation.  Up to four VCB01's may 
  be selected for testing at one time.  Testing mode is sequential, 
  with each device being tested once per pass.

1 Device

  This program will run only on a MicroVAX 1 computer and with a Vax 
  Diagnostic Supervisor of version 6.12 or later.  This program is a 
  level 3 diagnostic.

  This program will support the Q-BUS Video Sub-System -VCB01- (M7602) 
  device only.

2 VCB01

  Description:  VCB01 Video Controller Board (VCB)
  Link:         HUB
  Generic name: VCan
  Information:  QBUS CSR Register address [Octal 760000-777776]<777200>
  Tested by:    EHXVS

1 Requirements

  Hardware:    MicroVAX 1 processor with 512Kb of memory.
               From one to four VCB01 (M7602) devices.

  Software:    Vax Diagnostic Supervisor V6.12 or later.

1 Event_flags

  Event Flag 1

  When this flag is set, it informs the diagnostic program that loopback
  connectors have been installed.  This will allow the external circuits 
  of the device to be tested and also, the mouse counter test will be 
  executed.

  Event Flag 2

  When this flag is set, it allows the operator to change the amount of
  time that the Refresh test runs.  The default amount of time is twenty
  seconds, the event flag allows the operator to set the default time 
  from 0 - 327679 seconds (3 days).  Good for weekend testing of chip
  refresh circuitry.

  Event Flag 3

  When this flag is set, it informs the diagnostic program to issue a
  summary message every four passes; no prompt is used.  Typically used 
  in conjunction with the 'SET IE3' command to disable all reporting 
  except errors.

  Event Flag 4

  When this flag is set, it informs the diagnostic program to issue a
  prompt to ask the operator how many passes to execute between summary 
  messages.  Typically used in conjunction with the 'SET IE3' command 
  to disable all reporting except errors.

  Event Flag 5

  When this flag is set, it informs the diagnostic program that none of
  the selected VCB01 modules under test are console devices.  This flag
  should be set when a regular console terminal is connected to the
  MicroVAX to run the diagnostics.

1 Quick

  This diagnostic does not use the VDS QUICK-pass flag.

1 Summary

  Summary messages are printed at the end of each pass for all selected
  devices.  Error totals are cumulative.  Summary messages may be inhibited
  by issuing the following command to the Supervisor: DS> SET IES .
  Summary messages may also be issued every x number of passes through
  the use of Event Flag 4 (see above).

1 Sections

  There are nine sections provided in the diagnostic.  The section names
  are as follows; DEFAULT, MEMORY, DUART, INTERRUPT, CURSOR, MOUSE, REFRESH,
  OPERATOR and ALIGN.  All tests are contained in the DEFAULT section with the
  exception of the alignment pattern generator and the operator intervention
  tests.  These tests are contained within the ALIGN and OPERATOR sections
  respectively.

  With the exception of DEFAULT and OPERATOR the section names signify the 
  part of the device which they test.  ie. the INTERRUPT section contains
  the tests which use interrupts during its testing.

2 Default
   
  The DEFAULT section contains all of the standard run tests; tests one (1) 
  thru twelve (12).  This is the section that is run when the simple command 
  of START or RUN EHXVS is entered.
  

2 Refresh

  The REFRESH section contains a memory refresh circuitry test.  If event
  Flag 2 is set the operator will be asked how long he wishes the test to run.
  If the Flag is not set the test will run for the default of 20 seconds.

2 OPERATOR

  The OPERATOR section contains the interactive mouse and keyboard test.
  To exit this test either press the leftmost mouse key and/or the Ctrl 
  key on keyboard three consecutive times.

2 Align

  The ALIGN section contains the Alignment Pattern Generator only.  The 
  section will put the alignment pattern on the screen and then wait for
  a ^C to return to the DS> prompt.

1 Run_times

  The run time for the DEFAULT section is approximately 2 minutes.  Both the
  OPERATOR and ALIGN sections are operator dependent.

1 Tests

  The following is a list of the tests contained in the diagnostic EHXVS.

    Test #    Test Name                               Sections *=DEFAULT
    --------  --------------------------------------  ------------------

    Test 1:   Register Probe Test                     * Memory
    Test 2:   Memory Bitmap Test                      * Memory
    Test 3:   Interrupt Controller Register R/W Test  * Interrupt
    Test 4:   Interrupt Controller Interrupt Test     * Interrupt
    Test 5:   Duart Register R/W Test                 * Duart
    Test 6:   Duart Loopback Test                     * Duart
    Test 7:   Duart Interrupt Driven Loopback Test    * Duart,Interrupt
    Test 8:   Cursor Position Test                    * Cursor
    Test 9:   Scan Line Map Test                      * Memory
    Test 10:  Mouse Counter Test                      * Mouse,Interrupt
    Test 11:  Memory Refresh Test                     * Memory,Refresh
    Test 12:  Visual Video Odd/Even Generator Test    * Memory
    Test 13:  Mouse & Keyboard Interaction Tests      Operator
    Test 14:  Alignment Pattern Generator             Align

1 Attach

  Attaching the VCB01 to the MicroVAX 1 CPU...

    DIAGNOSTIC SUPERVISOR.  ZZ-EHSAA-V6.12-001  26-APR-1984 00:00:03
    DS> ATT VCB01 HUB VCB0 777200 100   ; attach the VCB01

  Or:
    DS> ATTACH                          ; attach a device
    Device type? VCB01                  ; the option type is VCB01
    Device link? HUB                    ; the option is linked to HUB
    Device name? VCB0                   ; the option is named VCan
    CSR? 777200                         ; the CSR address is 777200 octal
    Vector? 100                         ; the vector is 100            

  Then:
    DS> SELECT VCB0                     ; select the unit to be Tested
    DS> RUN EHXVS                       ; start the Diagnostic run

1 Notes

    When the VCB01 is the console device, and the diagnostic is testing
    the console VCB01 device, ALL control C's will automatically abort
    the Diagnostic session and return with the Supervisor prompt (DS>).
    In addition, when the VCB01 is the console device, the wait LED on the
    LK201 keyboard will light whenever any test is running.  It will 
    extinguish after the test is finished.

    If the VCB01 is NOT the console device, then Event Flag 5 must be set
    prior to running the Diagnostic.

    Test 12 is for visual inspection.  The screen should be
    completely full of a vertical pattern.  Should the top and/or
    the bottom of the screen not have a pattern on it then one of
    the video output shift registers is in error.  The top half 
    signifies the odd shifter while the bottom the even.

DUA1:<SYS0.SYSMAINT>EVRMA.HLP;1
===============================
1 HELP
   The Level 3 Exerciser for RC25 (EVRMA) is a "parallel" diagnostic
   designed to verify the integrity of one or several drives under test,
   and to detect faults at the functional level only. Under the Multi-
   Drive Subtest, the program should give a clear indication as to how
   an RC25 drive will perform under stressful operating system conditions.
   The Multi-Drive Subtest simulates these conditions by issuing a heavy
   load of MSCP I/O commands to all online units. The user can control
   many of the I/O command parameters through the Manual Intervention
   Test (/SEC:MANUAL) including function (write-only, read-only, writes
   and reads, write-compares, read-compares), disk block selection
   (random vs. sequential), track number limits, and the selection of
   data patterns. In addition, the user can choose instead to run the
   DM Exerciser Subtest. This subtest consists of the ROM-resident Front
   Panel Test running in the DM (Diagnostic Machine) under host control.

   This program can test up to 4 LESI controllers (4 different IP
   addresses), each controller having up to 2 drives (1 master and 1
   slave), and each drive with 2 platters (RC25 removable and RCF25
   fixed).

1 DEVICES
   EVRMA supports the following devices:

   Device type       Device name
   -----------       -----------

   LESI  - RC(F)25 controller    DAa
   RC25 - removable disk         DAan
   RCF25 - fixed disk         DAan

   where a = controller designation (A, B, etc.)
         n = unit number (from unit plug)

1 ATTACH
   The ATTACH command is used for specifying descriptions of devices
   existing on the system under test. A device cannot be accessed by
   a diagnostic program unless it has first been attached. Attaching
   a device generally consists of issuing a set of ATTACH commands so
   that a series of links can be established from the processor to the
   device. The link that is closest to the processor is a
   pseudo-connection known as "HUB". All devices must be ultimately
   linked to HUB. The format of the ATTACH command is as follows:

   ATTACH dev-type dev-link generic-name [device-specific-info]

   In order for EVRMA to exercise RC25 drive-units, the following
   devices must first be ATTACHed:

      UBA (UNIBUS adapter)   - must be ATTACHed to the HUB
      LESI (RC25 controller) - must be ATTACHed to the UBA
      RC25 (removable disk)  - must be ATTACHed to the LESI
      RCF25 (fixed disk)     - must be ATTACHed to the LESI

   NOTE: For microVAX, there are no UNIBUS adapters; attach the LESI
   directly to the HUB.

2 UBA
   * = not applicable for this model

   DS> ATTACH
   Device type? DW780   ( or )   DW750   ( or )   DW730
   Device link? HUB              HUB              HUB
   Device name? DW0              DW0              DW0
   TR?          3                *                *
   BR?          4                5                *

   NOTE: The UBA is not ATTACHed under microVAX.

2 LESI
   Example:

   DS> ATTACH     ! Attach
   Device type? LESI !     the LESI controller
   Device link? DW0  !     to the UNIBUS adapter
   Device name? DAa  ! a = controller designation (A, B, etc.)
   IP? 772150     ! Typical IP address
   VECTOR? 154    ! Typical vector address
   BR? 5       ! Typical bus request level

   NOTE: For microVAX, attach the LESI directly to the HUB.

2 RC25
   Example:

   DS> ATTACH     ! Attach the RC25 removable disk to its
   Device type? RC25 !     LESI controller (DAa)
   Device link? DAa  ! a = controller designation (A, B, etc.)
   Device name? DAan ! n = even unit number from unit plug

2 RCF25
   Example:

   DS> ATTACH     ! Attach the RCF25 fixed disk to its
   Device type? RCF25   !     LESI controller (DAa)
   Device link? DAa  ! a = controller designation (A, B, etc.)
   Device name? DAan ! n = odd unit number from unit plug

1 SELECT
   Selects devices for testing. A diagnostic program will only test
   devices which have been SELECTed. Devices specified in the SELECT
   command must have been previously ATTACHed. Multiple devices may be
   specified in one command.

   For EVRMA, all disks (RC25 and RCF25) to be exercised must be
   SELECTed. SELECTing LESI controllers is optional and has no effect
   on program operation.

   General Format:

      SELECT DAa, DAan [, DAan, ...]

   Examples:

      SELECT DAA, DAA0, DAA1
      SELECT DAB4, DAB5

1 EVENT
   EVRMA does not support any user-alterable event flags.

1 QUICK
   EVRMA does not support use of the QUICK flag.

1 SECTION
   Defines the sections (/SECTION qualifier on RUN or START) which this
   program supports. The Level 3 Exerciser for RC25 (EVRMA) supports the
   MANUAL program section in addition to the DEFAULT program section.
   The MANUAL program section allows the user to change various program
   parameters and options before any testing takes place.

2 DEFAULT
   This section will exercise all SELECTed RC25 (and RCF25) platters
   using default program parameters and options.

   To run this section type:

   RUN EVRMA         or
   RUN EVRMA/SECTION:DEFAULT

   or you can type:
   
   LOAD EVRMA        then
   START          or
   START/SECTION:DEFAULT      or

2 MANUAL
   This section allows the operator to view and/or change various soft
   parameters and options before any testing takes place. A series of
   questions will be posed, along with the default answers and permissible
   range of values. To select the default answer to any question, simply
   type a carriage return. After all questions have been answered, the
   program proceeds with testing in the normal manner.

   To run this section, type:

   RUN EVRMA/SECTION:MANUAL

   or you can type:
   
   LOAD EVRMA     followed by
   START/SECTION:MANUAL

1 SUMMARY
   The SUMMARY command will cause the current Exerciser statistics to
   be printed on the console terminal. The actual format of the Summary
   Report depends on which subtest was run. The Multi-Drive Subtest does
   not keep the same set of statistics as the DM Exerciser Subtest.

2 MULTI-DRIVE
   ******************** S U M M A R Y   R E P O R T *******************
   ELAPSED TIME:  XX:XX:XX

              NO.     NO.   MBYTES  MBYTES   NO. HARD  NO. ERR
     UNIT    READS  WRITES   READ   WRITTEN   ERRORS     LOGS
   -------  ------  ------  ------  -------  --------  -------

   _DAannn  XXXXXX  XXXXXX  XXXXXX  XXXXXXX   XXXXXX   XXXXXXX
   _DAannn  XXXXXX  XXXXXX  XXXXXX  XXXXXXX   XXXXXX   XXXXXXX
   _DAannn  XXXXXX  XXXXXX  XXXXXX  XXXXXXX   XXXXXX   XXXXXXX
      .        .       .       .       .         .        .
      .        .       .       .       .         .        .
      .        .       .       .       .         .        .

   N SYMBOL ECC ERRORS:

           ECC
          FIELD   N =    N =    N =    N =    N =    N =    N =    N =
    UNIT   ONLY    1      2      3      4      5      6      7      8
   -----  -----  -----  -----  -----  -----  -----  -----  -----  -----

   _DAan  XXXXX  XXXXX  XXXXX  XXXXX  XXXXX  XXXXX  XXXXX  XXXXX  XXXXX
   _DAan  XXXXX  XXXXX  XXXXX  XXXXX  XXXXX  XXXXX  XXXXX  XXXXX  XXXXX
   _DAan  XXXXX  XXXXX  XXXXX  XXXXX  XXXXX  XXXXX  XXXXX  XXXXX  XXXXX
     .      .      .      .      .      .      .      .      .      .
     .      .      .      .      .      .      .      .      .      .
     .      .      .      .      .      .      .      .      .      .

2 DM_EXERCSIER
   ******************** S U M M A R Y   R E P O R T *******************
   ELAPSED TIME:  XX:XX:XX

            NO.      NO.      NO.    MBYTES  MBYTES   NO. HARD  NO. SOFT
    UNIT   READS   WRITES    SEEKS    READ   WRITTEN   ERRORS    ERRORS
   -----  -------  -------  -------  ------  -------  --------  --------

   _DAan  XXXXXXX  XXXXXXX  XXXXXXX  XXXXXX  XXXXXXX   XXXXXX    XXXXXX
   _DAan  XXXXXXX  XXXXXXX  XXXXXXX  XXXXXX  XXXXXXX   XXXXXX    XXXXXX
   _DAan  XXXXXXX  XXXXXXX  XXXXXXX  XXXXXX  XXXXXXX   XXXXXX    XXXXXX
     .       .        .        .        .       .         .         .
     .       .        .        .        .       .         .         .
     .       .        .        .        .       .         .         .

DUA1:<SYS0.SYSMAINT>EVRMB.HLP;1
===============================
1 ATTACH
           The ATTACH command is  used  for  specifying  descriptions  of
           devices existing on the system under test.  A device cannot be
           accessed by a diagnostic program  unless  it  has  first  been
           attached.

           Attaching a device generally consists  of  issuing  a  set  of
           ATTACH  commands  so that a series of links can be established
           from the processor to the device.  The link that is closest to
           the  processor  is  a  pseudo-connection  known as "HUB".  All
           devices must be ultimately linked to  HUB.   This  concept  is
           illustrated by the example below.


      Format:

           ATTACH uut-type link-name generic-name [device-specific]

2 780
     DS> ATTACH
     Device type? DW780
     Device link? HUB
     Device name? DW0
     TR?      3
     BR?      4

     DS> ATTACH   
     Device type? LESI
     Device link? DW0
     Device name? DAA
     IP?   772150
     Vector?     154
     Br?      5

     DS> ATTACH
     Device type? RC25
     Device link? DAA
     Device name? DAA0

     DS> ATTACH
     Device type? RCF25
     Device link? DAA
     Device name? DAA1

2 750
     DS> ATTACH
     Device type? DW750
     Device link? HUB
     Device name? DW0

     DS> ATTACH   
     Device type? LESI
     Device link? DW0
     Device name? DAA
     IP?   772150
     Vector?     154
     Br?      5

     DS> ATTACH
     Device type? RC25
     Device link? DAA
     Device name? DAA0

     DS> ATTACH
     Device type? RCF25
     Device link? DAA
     Device name? DAA1

2 730
     DS> ATTACH
     Device type? DW730
     Device link? HUB
     Device name? DW0

     DS> ATTACH   
     Device type? LESI
     Device link? DW0
     Device name? DAA
     IP?   772150
     Vector?     154
     Br?      5

     DS> ATTACH
     Device type? RC25
     Device link? DAA
     Device name? DAA0

     DS> ATTACH
     Device type? RCF25
     Device link? DAA
     Device name? DAA1

2 725
     DS> ATTACH
     Device type? DW730
     Device link? HUB
     Device name? DW0

     DS> ATTACH   
     Device type? LESI
     Device link? DW0
     Device name? DAA
     IP?   772150
     Vector?     154
     Br?      5

     DS> ATTACH
     Device type? RC25
     Device link? DAA
     Device name? DAA0

     DS> ATTACH
     Device type? RCF25
     Device link? DAA
     Device name? DAA1

2 MicroVax
     DS> ATTACH   
     Device type? LESI
     Device link? HUB
     Device name? DAA
     UDAIP?   772150
     Vector?     154
     Br?      5
     Burst_Rate?  2

     DS> ATTACH
     Device type? RC25
     Device link? DAA
     Device name? DAA0

     DS> ATTACH
     Device type? RCF25
     Device link? DAA
     Device name? DAA1


1 SELECT
           Selects devices for testing.  A diagnostic program  will  only
           test  devices  which have been selected.  Devices specified in
           the SELECT command must have been previously ATTACHed.

     Format:

           SELECT DAA, DAA0, DAA1

1 DEVICES
       EVRMB supports DA devices

1 EVENT

       If event flag 2 is set, then the operator will be prompted
       for number of retries and whether to continue the test or
       abort the program and also questions to include area tested
       in some tests.

1 HELP

The RC25 front end host diagnostic (EVRMB) is designed to test the
RC25 disk drive subsystem.  Tests are performed to verify that:

a) The processor can properly communicate with the controller thru
   the adapter card.

b) The RC25 drive can seek and head select properly.

c) The RC25 conforms to the specified seek and rotational times.

d) The RC25 controller can perform certain basic functions in
   response to MSCP commands.


For each of the folowing parameters, type "HELP EVRMB parameter"


1 QUICK
There is no quick flag usage employed by this program.

1 SECTION
Defines the formatter sections (/SECTION qualifier on RUN or START)
which this formatter supports.  This formatter host code supports 
only the DEFAULT program section.

1 UNIT
One RC25 unit (UUT) is defined as a single platter. There are two
platters on one spindle in an RC25 drive. The RC25 controller may
have either one or two drives (two or four platters). The unit
number for the RC25 platters come in pairs. The removable media 
has an even number and the fixed media has the sequentially following
odd number. A maximum of 16 units can be tested in sequence.

2 DEFAULT
This section will run all tests with the exception of manual test.

To run this section type:

        RUN EVRMB                       or
        RUN EVRMB/SECTION:DEFAULT       or

or you can type:
   
        LOAD EVRMB                      then
        START                           or
        START/SECTION:DEFAULT           or

2 CRD
This section will run tests intended for CRD.

To run this section type:

   RUN EVRMB/SECTION:CRD
or you can type:

   LOAD EVRMB
   START/SECTION:CRD

2 MANUAL
This section will run operator intervention test. This test is not
implemented in this revision.

1 SUMMARY
   EVRMB does not give summary report.


DUA1:<SYS0.SYSMAINT>EVRMC.HLP;1
===============================
1 ATTACH
           The ATTACH command is  used  for  specifying  descriptions  of
           devices existing on the system under test.  A device cannot be
           accessed by a diagnostic program  unless  it  has  first  been
           attached.

           Attaching a device generally consists  of  issuing  a  set  of
           ATTACH  commands  so that a series of links can be established
           from the processor to the device.  The link that is closest to
           the  processor  is  a  pseudo-connection  known as "HUB".  All
           devices must be ultimately linked to  HUB.   

2 780
     DS> ATTACH
     Device type? DW780
     Device link? HUB
     Device name? DW0
     TR?      3
     BR?      4

     DS> ATTACH   
     Device type? LESI
     Device link? DW0
     Device name? DAA
     IP?   772150
     Vector?     154
     Br?      5

     DS> ATTACH
     Device type? RC25
     Device link? DAA
     Device name? DAA0

     DS> ATTACH
     Device type? RCF25
     Device link? DAA
     Device name? DAA1

2 750
     DS> ATTACH
     Device type? DW750
     Device link? HUB
     Device name? DW0

     DS> ATTACH   
     Device type? LESI
     Device link? DW0
     Device name? DAA
     IP?   772150
     Vector?     154
     Br?      5

     DS> ATTACH
     Device type? RC25
     Device link? DAA
     Device name? DAA0

     DS> ATTACH
     Device type? RCF25
     Device link? DAA
     Device name? DAA1

2 730
     DS> ATTACH
     Device type? DW730
     Device link? HUB
     Device name? DW0

     DS> ATTACH   
     Device type? LESI
     Device link? DW0
     Device name? DAA
     IP?   772150
     Vector?     154
     Br?      5

     DS> ATTACH
     Device type? RC25
     Device link? DAA
     Device name? DAA0

     DS> ATTACH
     Device type? RCF25
     Device link? DAA
     Device name? DAA1

2 725
     DS> ATTACH
     Device type? DW730
     Device link? HUB
     Device name? DW0

     DS> ATTACH   
     Device type? LESI
     Device link? DW0
     Device name? DAA
     IP?   772150
     Vector?     154
     Br?      5

     DS> ATTACH
     Device type? RC25
     Device link? DAA
     Device name? DAA0

     DS> ATTACH
     Device type? RCF25
     Device link? DAA
     Device name? DAA1

2 MicroVax
     DS> ATTACH   
     Device type? LESI
     Device link? HUB
     Device name? DAA
     UDAIP?      772150
     Vector?     154
     Br?      5
     Burst_Rate?  2

     DS> ATTACH
     Device type? RC25
     Device link? DAA
     Device name? DAA0

     DS> ATTACH
     Device type? RCF25
     Device link? DAA
     Device name? DAA1


1 SELECT
           Selects devices for testing.  A diagnostic program  will  only
           test  devices  which have been selected.  Devices specified in
           the SELECT command must have been previously ATTACHed.

     Format:

           SELECT DAA0, DAA1

1 DEVICES
       EVRMC supports DA devices

1 EVENT
       Event flag number 21 is used by the operator to select one of the 
       two host operating modes.  EFN_21 state definition is as follows:

      EFN_21 = 0 :   UN-ATTENDED reformat mode
            -------------------------
            This is the hosts default operating mode.  When
            efn_21  is  cleared  the host will first prompt
            the operator  for the date.  The host will then
            automatically  instruct the  DM formatter to do
            a REFORMAT on all sub-systems  devices selected
            by the operator.

      EFN_21 = 1 :   ATTENDED format mode
            --------------------
            If  the  operator wishes to select a formatting
            mode other  than  a  REFORMAT mode, he/she must
            set  efn_21.  When  set  the  operater  has the
            responsibility  to  anwser  all   DM  formatter
            software parameter questions.

1 HELP
   This program will prepare RC25 media for use as addressable storage  by
   providing headers  and replacing of bad blocks.  This formatter will be
   composed of   two   sections;    a   host-resident   section,   and   a
   controller-resident DM code section.

   The host section will serially format up to sixteen RC25 subsystems  by
   downline-loading  the DM  code,  and  monitor  the  task.  The downline
   section will consist of overlays of DM code. The first of these will be
   down-line loaded to the drive itself,and accomplish the actual business
   of formatting,calling in additional overlays as needed, asking software
   parameters questions  and  printing  formatter  error and informational
   messages.
   
   There are three general modes of DM formatter operation and they are:

        o REFORMAT - This mode is used to format a medium which has been
          previously  formatted,  and  is  being  reformatted  to  clear
          existing data or to change the mode of the medium to 512 bytes
          per sector.  It assumes that the FCT is still intact.

        o RESTORE - This mode will only be run by DIGITAL  Manufacturing
          personnel.   It uses an external copy of the FCT produced when 
     the disk was manufactured and is stored offline to the    RC25 
     formatter.

        o RECONSTRUCT - This mode is used when none of the  other  modes
          is  possible.   It detects bad blocks by performing repetitive
          read checks of each sector.  For this  reason,  a  RECONSTRUCT
          run takes considerably longer than the other modes.

   There are two general modes of HOST operation and they are:

   o ATTENDED MODE- This is where an operator must be present at the
     console terminal  to respond to DM formatter software parameter
     questions.  In this HOST mode the operator can choose any of the
     three DM formatting modes.

   o UN-ATTENDED MODE- This is where the HOST will automaticaly answer
     DM  formatter  software parameter questions to perform a REFORMAT
     mode  to  all  units  selected  units  via  the hardware P_Tables.

   ********************************************************************
   *           WARNING              *
   *           -------              *
   *     Media formatting is considered to be an atomic operation     *
   *                          *
   *        - ONCE  STARTED IT CANNOT BE STOPPED -            *
   *                          *
   *          Aborting a format  will leave  media UNUSABLE    *
   *                          *
   ********************************************************************

For each of the folowing parameters, type "HELP EVRMC parameter"


1 QUICK
There is no quick flag usage employed by this host formatter code.

1 SECTION
Program sections are used within the $DS_BGNTEST macro to show which 
section a test belongs to.  This Host code has one test defined  and 
its section name is AZHOST.

To run this program type:

        RUN EVRMC                       or
        RUN EVRMC/SECTION:AZHOST        or

or you can type:
   
        LOAD EVRMC                      then
        START                           or
        START/SECTION:AZHOST            or


1 SUMMARY
All summary report coding is remote DM program driven.  Upon normal 
completion the formatter issues the following messages. All but the  
last are sent as DUP informational messages.  The last is sent as a  
DUP  termination  message.

          1.  "format completed"

          2.  "n revectored LBNs"
             Where n is the number of LBNs revectored in  the  user  data
             area.

          3.  "n primary revectored LBNs"
             Where n is the number of  LBNs  in  message  #2  which  were
             primary revectors.

          4.  "n secondary/tertiary revectored LBNs"
             Where n is the number of the LBNs in message #2  which  were
             secondary or tertiary revectors.

          5.  "n bad blocks in the RCT area due to data errors"
             Where n is the number of blocks in the total RCT area  which
             were bad due to errors in the data portion of their sectors.

          6.  "n bad blocks in the RCT due to header or timing errors"
             Where n is the number of blocks in the total RCT area  which
             were  bad  due  to  errors  in the header or timing areas of
             their sectors.

          7.  "n bad blocks in the DBN area due to data errors"
             Where n is the number of blocks in the DBN area  which  were
             bad due to errors in the data area of their sectors.

          8.  "n bad blocks in the  DBN  area  due  to  header  or  timing
             errors"
            Where n is the number of blocks in the DBN area  which  were
             bad  due  to  errors  in  the header or timing area of their
             sectors.

          9.  "n bad blocks in the XBN area due to data errors"
             Where n is the number of blocks in the XBN area  which  were
             bad due to errors in the data area of their sectors.

         10. "n bad blocks in the  XBN  area  due  to  header  or  timing
             errors"
             Where n is the number of blocks in the XBN area  which  were
             bad  due  to  errors  in  the header or timing area of their
             sectors.

    11. "n bad RBNS"
             Where n is the number of blocks in the RBN area  which  were
             bad due to errors in the data area of their sectors.

         12. "n blocks retried on the check pass"
             Where n is the number of blocks which had an  error  on  the
             first read attempt after formatting.

         13. "FCT used successfully" or

         14. "FCT was not used"
             Depending on the answers to the start-up questions  and  the
             availability  of  the  bad  block  information  (FCT).  This
             message has the DUP termination message code.


 
$ dir DUA1:<SYS0.SYSMAINT>

Directory DUA1:<SYS0.SYSMAINT>

EHXDH.EXE;1         EHXDH.HLP;1         EHXVS.EXE;1         EHXVS.HLP;1
EVRMA.EXE;1         EVRMA.HLP;1         EVRMB.EXE;1         EVRMB.HLP;1
EVRMC.EXE;1         EVRMC.HLP;1         

Total of 10 files.
 
$ dism dua1:
 
$ 
Simulation stopped, PC: 80007B06 (BRB 80007B06)
sim> att rq1 bl-t856d-de.img
sim> c
mou/over=id dua1:
 
%MOUNT-I-MOUNTED, MACROV       mounted on _DUA1:
 
$ dir dua1:<sys0.sysmaint>

Directory DUA1:<SYS0.SYSMAINT>

EHKAA.EXE;1         EHKMV.EXE;1         EHXMS.EXE;1         EHXQE.EXE;1

Total of 4 files.
 
$ 